Earlier quoted context omitted.
That's an excellent idea! It could be called I don't know... maybe "tmux"? Or "screen"?
Hmm, let's also allow you to edit text in those windows. And it should be extensible, of course. With a dialect of LISP! We could call it "emacs".
WTF: A personal information dashboard for your terminal
61–70 of 121 posts
Re: WTF: A personal information dashboard for your terminal
#62Anyone remembers NetBSD's wtf? http://netbsd.gw.com/cgi-bin/man-cgi/man?wtf+6+NetBSD-curren... $ wtf wtf WTF: {what,when,where,who,why} the fuck $ wtf bsd BSD: berkeley software distribution $ wtf linux wtf: I don't know what linux means!
Re: WTF: A personal information dashboard for your terminal
#63This is pretty neat. A dashboard screen isn't my style, but I've taught my assistant program to answer a lot of the same questions.
Re: WTF: A personal information dashboard for your terminal
#64I don't know any go. I was able to read everything, like I wrote the code. Is go usually that easy? If yes, I think I should learn it.
We also have to give credit to the author. Good programmers have programs that are easy to read and understand.
However like all languages that are easy to read, it can be deceptive. Once you dive into any big/complex project. Context and design decisions matter more than anything else.
Re: WTF: A personal information dashboard for your terminal
#65Re: WTF: A personal information dashboard for your terminal
#66I don't know any go. I was able to read everything, like I wrote the code. Is go usually that easy? If yes, I think I should learn it.
Re: WTF: A personal information dashboard for your terminal
#67Earlier quoted context omitted.
Got a good pointer to more details? I don't know anything about that spec.
See https://specifications.freedesktop.org/basedir-spec/basedir-... The main idea. You read $XDG_* variables, and use them if defined, and use spec defaults if not. It declutters $HOME from dot directories.
Re: WTF: A personal information dashboard for your terminal
#68I don't know any go. I was able to read everything, like I wrote the code. Is go usually that easy? If yes, I think I should learn it.
Yes. One of go's strengths is that there are very few tricks and the language is heavily biased towards easy reading over compact code.
Re: WTF: A personal information dashboard for your terminal
#69Can't this be made more general and modular by creating a windowing system for terminals first, and then write little programs that operate in that system?
At what point do we just say why not 'install a modern GUI'?
https://en.wikipedia.org/wiki/Openbox
Archbang , which uses openbox, is a good example of a distribution to try in a VM if anyone wants to see an example in action.
Re: WTF: A personal information dashboard for your terminal
#70This is pretty neat. A dashboard screen isn't my style, but I've taught my assistant program to answer a lot of the same questions.
Could you tell us more about your assistant program?
For instance, I found I was often asking my house a couple times throughout the day for the thermostat status when I was at work (I have a fairly temperature sensitive pet). This week I went ahead and just told it to go ahead and wrote a little 'status report' email, and then call for it a couple times a day in Windows Task Scheduler.