Differences between version 12 and predecessor to the previous major change of CommandLine.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 12 | Last edited on Sunday, January 11, 2004 4:33:31 am | by AristotlePagaltzis | Revert |
| Older page: | version 11 | Last edited on Friday, October 31, 2003 7:39:45 pm | by AristotlePagaltzis | Revert |
@@ -1,4 +1,6 @@
+;: "Linux supports the notion of a command line or a shell for the same reason that only children read books with only pictures in them. %%% Language, be it English or something else, is the only tool flexible enough to accomplish a sufficiently broad range of tasks." %%% -- ''Bill Garrett''
+
A CommandLine is a program interface which the user interacts with by entering commands as written text. The program then parses these commands and acts accordingly. Such an interface is usually highly scriptable - even if not intentionally so, but by virtue of redirection. When it is designed with scripting in mind, it is usually particularly powerful.
In Unix, nearly all tasks can and should be done on the CommandLine. Most people think of this as a pain, but there are many features to make working on the CommandLine more convenient and therefor efficient. Unix [Shell]s are lightyears ahead in terms of usability compared to the CommandLine interpreters MicrosoftCorporation has delivered with their [OperatingSystem]s in the past, although some of the more basic (and vital) conveniences such as TabCompletion have finally found their way into [Microsoft] CommandLine interpreters. (You're 30 years late, guys, but hey, welcome to the party anyway.)
