Sponsored Content
The Lounge What is on Your Mind? In defense of the command line Post 302547321 by Tal500 on Monday 15th of August 2011 07:21:40 AM
Old 08-15-2011
I do believe that command line will never die.
Take a look in TRANSMISSION, a bittorrent client.
It has daemon, library, command line use and graphical interface(both for QT and GTK).
Well, both GUI camp and CLI camp would love it. I think than every human "need" shell be in the 4th(of TRANSSMISION) or at least as library(so other developers can extend it to UI).
I'm a developer, and using common CLI, because I think it's easier for me to perform my own made scripts("compile"), and so on...
97% of my time on my Debian machine, a GNOME/Xfce terminal is opening, and if not, or I want do something in background, I can always type F9, and then Compiz Fusion widget layer is displayed. A command line waits for me(the cairo-dock CLI) whenever I need it.
I think a combination of GUI and CLI is the best approach.

Even when today GUI is getting smarter(multi-touch and full body), it's always recommended to save an icon in the panel for command line.
 

We Also Found This Discussion For You

1. Shell Programming and Scripting

sed command to replace a line at a specific line number with some other line

my requirement is, consider a file output cat output blah sdjfhjkd jsdfhjksdh sdfs 23423 sdfsdf sdf"sdfsdf"sdfsdf"""""dsf hellow there this doesnt look good et cetc etc etcetera i want to replace a line of line number 4 ("this doesnt look good") with some other line ... (3 Replies)
Discussion started by: vivek d r
3 Replies
wait(1) 						      General Commands Manual							   wait(1)

NAME
wait - await process completion SYNOPSIS
[pid] DESCRIPTION
If no argument is specified, waits until all processes (started with of the current shell have completed, and reports on abnormal termina- tions. If a numeric argument pid is given and is the process ID of a background process, waits until that process has completed. Other- wise, if pid is not a background process, exits without waiting for any processes to complete. Because the system call must be executed in the parent process, the shell itself executes without creating a new process (see wait(2)). Command-Line Arguments supports the following command line arguments: The unsigned decimal integer process ID of a command, whose termination is to wait for. WARNINGS
Some processes in a 2-or-more-stage pipeline may not be children of the shell, and thus cannot be waited for. SEE ALSO
csh(1), ksh(1), sh-posix(1), sh(1), wait(2). STANDARDS CONFORMANCE
wait(1)
All times are GMT -4. The time now is 11:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy