Actions

History::Command-line interface

::concepts

Command::shell    Commands::windows    Program::systems    System::which    Prompt::language    Programs::other

History The command-line interface evolved from a form of dialog once conducted by humans over teleprinter (TTY) machines, in which human operators remotely exchanged information, usually one line of text at a time. Early computer systems often used teleprinter machines as the means of interaction with a human operator. The computer became one end of the human-to-human teleprinter model. So instead of a human communicating with another human over a teleprinter, a human communicated with a computer.

In time, the actual mechanical teleprinter was replaced by a "glass tty" (keyboard and screen, but emulating the teleprinter), and then by a "smart" terminal (where a microprocessor in the terminal could address all of the screen, rather than only print successive lines). As the microcomputer revolution replaced the traditional

  1. REDIRECT

{{#invoke:Message box|mbox}}minicomputer + terminals

  1. REDIRECT

{{#invoke:Message box|mbox}}time sharing architecture, hardware terminals were replaced by terminal emulators — PC software that interpreted terminal signals sent through the PC's serial ports. These were typically used to interface an organization's new PC's with their existing mini- or mainframe computers, or to connect PC to PC. Some of these PCs were running Bulletin Board System software.

Early operating system CLIs were implemented as part of resident monitor programs, and could not easily be replaced. The concept of implementing the shell as a replaceable component is usually attributed to Multics.<ref>{{#invoke:citation/CS1|citation |CitationClass=web }}</ref>{{ safesubst:#invoke:Unsubst||$N=Better source |date=__DATE__ |$B= {{#invoke:Category handler|main}}[better source needed] }}

Early microcomputers themselves were based on a command-line interface such as CP/M, MS-DOS or AppleSoft BASIC. Throughout the 1980s and 1990s—especially after the introduction of the Apple Macintosh and Microsoft Windows—command line interfaces were replaced in popular usage by the Graphical User Interface. The command line remains in use, however, by system administrators and other advanced users for system administration, computer programming, and batch processing.

In November 2006, Microsoft released version 1.0 of Windows PowerShell (formerly codenamed Monad), which combined features of traditional Unix shells with their proprietary object-oriented .NET Framework. MinGW and Cygwin are open-source packages for Windows that offer a Unix-like CLI. Microsoft provides MKS Inc.'s ksh implementation MKS Korn shell for Windows through their Services for UNIX add-on.

Since 2001, the Macintosh operating system is based on a variation of Unix called Darwin. On these computers, users can access a Unix-like command-line interface called Terminal found in the Applications Utilities folder. This terminal uses bash by default.

File:Matlab7.4.png
Screenshot of the MATLAB 7.4 command-line interface and GUI

Command-line interface sections
Intro  Advantages  Criticisms  Operating system command-line interfaces  Application command-line interfaces  History  Usage  Anatomy of a shell CLI  Command-line interpreter  Scripting  Other command-line interfaces  See also  References  External links  

History
PREVIOUS: Application command-line interfacesNEXT: Usage
<<>>