Linked by Thom Holwerda on Thu 16th Mar 2006 22:24 UTC, submitted by Valour
"There are several possible reasons why you might choose to use the command line interface as your desktop environment. For one thing, it uses less electricity, so you could maximize battery life on your laptop computer. Secondly, it forces you to think about your operating system and directory structure in a totally different way than a GUI does; this could greatly enhance your understanding of GNU/Linux and cause you to be more creative in your technological problem solving. And thirdly, everyone will think you're a supreme computer genius for ditching X11 for the CLI. People passing by your desk will think you're some kind of computer god. Who doesn't want that?"
Thread beginning with comment 105267
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2006-02-03
Once you suspend a task with Ctrl-z, you can tell it to resume execution in the background with the 'bg' command. The equivalent 'fg' command resumes execution in the foreground.
You can also tell bg and fg to act on a particular job--e.g., 'fg %1' would bring job 1 to the foreground.
RE[3]: Re: RE[5]: hmm...
by hobgoblin on Fri 17th Mar 2006 11:21
in reply to "RE[2]: Re: RE[4]: hmm..."
Member since:2005-07-06
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-06
thats why it would work best in combo with say the ability to take arguments after the fact (my firefox new tab example)...
all in all your problems are mostly one of communication, not between the app and the cli, but between the cli and the gui manager (alltho it can allso be between the app and the cli).
its all the same prosess, so if ever a window is drawn based on a started prosess, the gui manager tells the cli that it happens and the cli puts the prosess into the background.
alternativly the app tells the cli that it wants to run in the background. this signal can be sendt whenever a window is created...
well there is allso the ctrl+z combo, that will send any console hogging prosess to the background. problem is that it allso tells the prosess to suspend operation iirc.
but i was not realy looking at it from a unix standpoint but from a concept standpoint. as in something buildt from scratch to have this ability...
im starting to see the problems of X11, its basicly living its own life. still, i have allways loved the idea of the GUI being a prosess running on top of the kernel rather then being part of it like we see in windows. it allows so much flexibility...