Linked from

The 14 pages that link to Command-line interface, each with the reason it gives.

• Application programming interfaceCompared with: A command-line interface serves human operators, while an API primarily serves software.

• Graphical user interfaceCompared with: It performs many of the same computing tasks through typed instructions instead of visual controls.

• User interfaceCompared with: It replaces visible controls with typed commands and rewards command knowledge.

• Voice user interfaceCompared with: It shares command-based control with voice but requires typed input.

• MS-DOSNarrower topic: MS-DOS made this interaction style familiar to generations of PC users.

• Integrated development environmentCompared with: Command-line tools can perform IDE tasks separately, without a unified graphical workspace.

• Input deviceCompared with: It is a software interaction method, not a physical input device.

• Xerox AltoCompared with: The Alto's graphical interaction offered an alternative to the command-driven systems common at the time.

• DashboardCompared with: It requires explicit commands rather than presenting system status visually at a glance.

• DOSNarrower topic: DOS commonly accepts commands through a text prompt rather than a graphical desktop.

• ExecutableRelated: Shells commonly launch executables in response to command-line invocations.

• Shell scriptNarrower topic: A shell script automates commands normally entered through this interface.

• WinRARRelated: RAR command-line tools support scripted archive creation and extraction.

• Tool (computing)Related: Many tools are operated through typed commands rather than graphical controls.