Command-line interface - Revision history

148.252.146.66: /* Operating system command-line interfaces /Deleted a paragraph which was out of place, wrong, confused, confusing and without any references. A shell usually has a UI which can be a command line interface or a GUI but a shell is NOT* a UI, it is a command interpreter/processor.

2025-06-17T09:18:01Z

Operating system command-line interfaces: Deleted a paragraph which was out of place, wrong, confused, confusing and without any references. A shell usually has a UI which can be a command line interface or a GUI but a shell is *NOT* a UI, it is a command interpreter/processor.

← Previous revision		Revision as of 09:18, 17 June 2025
Line 25:		Line 25:

	Examples of command-line interpreters include Nushell, [[Digital Equipment Corporation\|DEC's]] [[DIGITAL Command Language]] (DCL) in [[OpenVMS]] and [[RSX-11]], the various [[Unix shell]]s ([[Bourne shell\|sh]], [[KornShell\|ksh]], [[C shell\|csh]], [[tcsh]], [[zsh]], [[Bash (Unix shell)\|Bash]], etc.), [[CP/M]]'s [[Console Command Processor\|CCP]], [[DOS]]' [[COMMAND.COM]], as well as the [[OS/2]] and the Windows [[CMD.EXE]] programs, the latter groups being based heavily on DEC's RSX-11 and [[RSTS/E\|RSTS]] CLIs. Under most operating systems, it is possible to replace the default shell program with alternatives; examples include [[4DOS]] for DOS, [[4OS2]] for OS/2, and [[Take Command Console\|4NT / Take Command]] for Windows.		Examples of command-line interpreters include Nushell, [[Digital Equipment Corporation\|DEC's]] [[DIGITAL Command Language]] (DCL) in [[OpenVMS]] and [[RSX-11]], the various [[Unix shell]]s ([[Bourne shell\|sh]], [[KornShell\|ksh]], [[C shell\|csh]], [[tcsh]], [[zsh]], [[Bash (Unix shell)\|Bash]], etc.), [[CP/M]]'s [[Console Command Processor\|CCP]], [[DOS]]' [[COMMAND.COM]], as well as the [[OS/2]] and the Windows [[CMD.EXE]] programs, the latter groups being based heavily on DEC's RSX-11 and [[RSTS/E\|RSTS]] CLIs. Under most operating systems, it is possible to replace the default shell program with alternatives; examples include [[4DOS]] for DOS, [[4OS2]] for OS/2, and [[Take Command Console\|4NT / Take Command]] for Windows.

	Although the term ''shell'' is often used to describe a command-line interpreter, strictly speaking, a ''shell'' can be any program that constitutes the user interface, including fully graphically oriented ones. For example, the default Windows GUI is a shell program named [[EXPLORER.EXE]], as defined in the SHELL=EXPLORER.EXE line in the WIN.INI configuration file. These programs are shells, but not CLIs.

	===Application command-line interfaces===		===Application command-line interfaces===

Strawbe Jary: Spelling/grammar/punctuation/typographical correction

2025-06-13T12:59:06Z

Spelling/grammar/punctuation/typographical correction

← Previous revision		Revision as of 12:59, 13 June 2025
Line 6:		Line 6:
	A '''command-line interface''' ('''CLI''') is a means of interacting with [[software]] via [[command (computing)\|commands]] {{endash}} each formatted as a line of text. Command-line interfaces emerged in the mid-1960s, on [[computer terminal]]s, as an interactive and more user-friendly alternative to the non-interactive mode available with [[punched cards]].<ref>{{Cite web \|title=The evolution of command line interface (CLI): A historical insight {{!}} Contentstack \|url=https://www.contentstack.com/blog/tech-talk/the-evolution-of-command-line-interface-cli-a-historical-insight \|access-date=2025-01-28 \|website=www.contentstack.com \|language=en}}</ref>		A '''command-line interface''' ('''CLI''') is a means of interacting with [[software]] via [[command (computing)\|commands]] {{endash}} each formatted as a line of text. Command-line interfaces emerged in the mid-1960s, on [[computer terminal]]s, as an interactive and more user-friendly alternative to the non-interactive mode available with [[punched cards]].<ref>{{Cite web \|title=The evolution of command line interface (CLI): A historical insight {{!}} Contentstack \|url=https://www.contentstack.com/blog/tech-talk/the-evolution-of-command-line-interface-cli-a-historical-insight \|access-date=2025-01-28 \|website=www.contentstack.com \|language=en}}</ref>

	For a long time, a CLI was the most common interface for software, but today a [[graphical user interface]] (GUI) is more common. ~~None-the-less~~, many programs such as [[operating system]] and [[software development]] [[utility software\|utilities]] still provide CLI.		For a long time, a CLI was the most common interface for software, but today a [[graphical user interface]] (GUI) is more common. Nonetheless, many programs such as [[operating system]] and [[software development]] [[utility software\|utilities]] still provide CLI.

	A CLI enables [[automation\|automating]] [[computer program\|programs]] since commands can be stored in a [[scripting language\|script]] [[computer file\|file]] that can be used repeatedly. A script allows its contained commands to be executed as group; as a program; as a command.		A CLI enables [[automation\|automating]] [[computer program\|programs]] since commands can be stored in a [[scripting language\|script]] [[computer file\|file]] that can be used repeatedly. A script allows its contained commands to be executed as group; as a program; as a command.

66.215.184.32: Added author's name to citation.

2025-05-23T11:52:56Z

Added author's name to citation.

← Previous revision		Revision as of 11:52, 23 May 2025
Line 356:		Line 356:
	<ref name="Kerninghan_1984">{{cite book \|author-first1=Brian W. \|author-last1=Kernighan \|author-link1=Brian Kernighan \|author-first2=Rob \|author-last2=Pike \|author-link2=Rob Pike \|title=The UNIX Programming Environment \|location=Englewood Cliffs \|publisher=[[Prentice-Hall]] \|date=1984 \|isbn=0-13-937699-2 \|url=https://archive.org/details/unixprogramminge0000kern \|url-access=registration}}</ref>		<ref name="Kerninghan_1984">{{cite book \|author-first1=Brian W. \|author-last1=Kernighan \|author-link1=Brian Kernighan \|author-first2=Rob \|author-last2=Pike \|author-link2=Rob Pike \|title=The UNIX Programming Environment \|location=Englewood Cliffs \|publisher=[[Prentice-Hall]] \|date=1984 \|isbn=0-13-937699-2 \|url=https://archive.org/details/unixprogramminge0000kern \|url-access=registration}}</ref>
	<ref name="Pouzin">{{cite web \|author-last=Pouzin \|author-first=Louis \|title=The Origin of the Shell \|work=Multicians.org \|url=http://www.multicians.org/shell.html \|access-date=2013-09-22 \|archive-date=2017-12-21 \|archive-url=https://web.archive.org/web/20171221142542/http://www.multicians.org/shell.html \|url-status=live }}</ref>		<ref name="Pouzin">{{cite web \|author-last=Pouzin \|author-first=Louis \|title=The Origin of the Shell \|work=Multicians.org \|url=http://www.multicians.org/shell.html \|access-date=2013-09-22 \|archive-date=2017-12-21 \|archive-url=https://web.archive.org/web/20171221142542/http://www.multicians.org/shell.html \|url-status=live }}</ref>
	<ref name="Betanews">{{cite web\|title=Remembering Windows 95's launch 15 years later\|date=24 August 2010\|url=http://betanews.com/2010/08/24/remembering-windows-95-s-launch-15-years-later/\|access-date=2015-02-18 \|archive-date=2015-02-18 \|archive-url=https://web.archive.org/web/20150218221032/http://betanews.com/2010/08/24/remembering-windows-95-s-launch-15-years-later/\|url-status=live}}</ref>		<ref name="Betanews">{{cite web\|author-first1=Joe\|author-last1=Wilcox\|website=BetaNews\|title=Remembering Windows 95's launch 15 years later\|date=24 August 2010\|url=http://betanews.com/2010/08/24/remembering-windows-95-s-launch-15-years-later/\|access-date=2015-02-18 \|archive-date=2015-02-18 \|archive-url=https://web.archive.org/web/20150218221032/http://betanews.com/2010/08/24/remembering-windows-95-s-launch-15-years-later/\|url-status=live}}</ref>
	<ref name="Microsoft_History">{{cite web \|title=A history of Windows \|website=windows.microsoft.com \|url=http://windows.microsoft.com/en-US/windows/history#T1=era0 \|archive-url=https://web.archive.org/web/20150301073112/http://windows.microsoft.com/en-US/windows/history \|archive-date=2015-03-01}}</ref>		<ref name="Microsoft_History">{{cite web \|title=A history of Windows \|website=windows.microsoft.com \|url=http://windows.microsoft.com/en-US/windows/history#T1=era0 \|archive-url=https://web.archive.org/web/20150301073112/http://windows.microsoft.com/en-US/windows/history \|archive-date=2015-03-01}}</ref>
	<ref name="Microsoft_POSIX">{{cite web \|title=Windows POSIX shell compatibility \|date=22 February 2013 \|url=https://technet.microsoft.com/en-us/library/cc754351.aspx \|access-date=2017-08-26 \|archive-date=2017-07-03 \|archive-url=https://web.archive.org/web/20170703090254/https://technet.microsoft.com/en-us/library/cc754351.aspx \|url-status=live }}</ref>		<ref name="Microsoft_POSIX">{{cite web \|title=Windows POSIX shell compatibility \|date=22 February 2013 \|url=https://technet.microsoft.com/en-us/library/cc754351.aspx \|access-date=2017-08-26 \|archive-date=2017-07-03 \|archive-url=https://web.archive.org/web/20170703090254/https://technet.microsoft.com/en-us/library/cc754351.aspx \|url-status=live }}</ref>

Guy Harris: /* Other command-line interfaces */ Get rid of trailing space.

2025-05-23T02:34:08Z

Other command-line interfaces: Get rid of trailing space.

← Previous revision		Revision as of 02:34, 23 May 2025
Line 306:		Line 306:
	Programs like BASIC, [[diskpart]], [[Edlin]], and QBASIC all provide command-line interfaces, some of which use the system shell. Basic is modeled on the default interface for 8-bit Intel computers. Calculators can be run as command-line or dialog interfaces.		Programs like BASIC, [[diskpart]], [[Edlin]], and QBASIC all provide command-line interfaces, some of which use the system shell. Basic is modeled on the default interface for 8-bit Intel computers. Calculators can be run as command-line or dialog interfaces.

	[[Emacs]] provides a command-line interface in the form of its minibuffer. Commands and arguments can be entered using Emacs standard text editing support, and output is displayed in another buffer.		[[Emacs]] provides a command-line interface in the form of its minibuffer. Commands and arguments can be entered using Emacs standard text editing support, and output is displayed in another buffer.

	There are a number of text mode games, like ''[[Colossal Cave Adventure\|Adventure]]'' or ''[[King's Quest#Series\|King's Quest 1-3]]'', which relied on the user typing commands at the bottom of the screen. One controls the character by typing commands like 'get ring' or 'look'. The program returns a text which describes how the character sees it, or makes the action happen. The [[text adventure]] ''[[The Hitchhiker's Guide to the Galaxy (video game)\|The Hitchhiker's Guide to the Galaxy]]'', a piece of [[interactive fiction]] based on [[Douglas Adams\|Douglas Adam's]] book of the same name, is a teletype-style command-line game.		There are a number of text mode games, like ''[[Colossal Cave Adventure\|Adventure]]'' or ''[[King's Quest#Series\|King's Quest 1-3]]'', which relied on the user typing commands at the bottom of the screen. One controls the character by typing commands like 'get ring' or 'look'. The program returns a text which describes how the character sees it, or makes the action happen. The [[text adventure]] ''[[The Hitchhiker's Guide to the Galaxy (video game)\|The Hitchhiker's Guide to the Galaxy]]'', a piece of [[interactive fiction]] based on [[Douglas Adams\|Douglas Adam's]] book of the same name, is a teletype-style command-line game.

Guy Harris: /* CLI and resource protection / Note that not all* CLIs support PATH; give Unix-like systems and Windows as systems that support PATH, and speak of PATH and equivalents for other systems that allow this. In the "restrict available commands" paragraph, mention restricted shells, where setting PATH to include only directories with permissible commands limits the user's ability to run other commands.

2025-05-23T02:16:05Z

CLI and resource protection: Note that not *all* CLIs support PATH; give Unix-like systems and Windows as systems that support PATH, and speak of PATH *and equivalents* for other systems that allow this. In the "restrict available commands" paragraph, mention restricted shells, where setting PATH to include only directories with permissible commands limits the user's ability to run other commands.

← Previous revision		Revision as of 02:16, 23 May 2025
Line 96:		Line 96:

	===CLI and resource protection===		===CLI and resource protection===
	~~One~~ can modify the set of available commands by modifying which paths appear in the [[PATH (variable)\|PATH]] environment variable. ~~Under~~ Unix, commands also need be marked as [[executable]] files. The directories in the path variable are searched in the order they are given. By re-ordering the path, one can run e.g. \OS2\MDOS\E.EXE instead of \OS2\E.EXE, when the default is the opposite. Renaming of the executables also works: people often rename their favourite editor to EDIT, for example.		On some systems, such as [[Unix-like]] systems or Windows, one can modify the set of available commands by modifying which paths appear in the [[PATH (variable)\|PATH]] environment variable or its equivalent. On Unix-like systems, commands also need be marked as [[executable]] files. The directories in the path variable are searched in the order they are given. By re-ordering the path, one can run e.g. \OS2\MDOS\E.EXE instead of \OS2\E.EXE, when the default is the opposite. Renaming of the executables also works: people often rename their favourite editor to EDIT, for example.

	The command line allows one to restrict available commands, such as access to advanced internal commands. The Windows [[CMD.EXE]] ~~does~~ ~~this~~. Often, shareware programs will limit the range of commands, including printing a command 'your administrator has disabled running batch files' from the prompt.{{Clarify\|reason=The sentence seems ambigious and confuses me. Does "including printing a command 'your administrator has disabled running batch files' from the prompt" describe an act of limiting the range of commands, or does it rather describe a command that a user may (try to) give which is then limited?\|date=July 2021}}		The command line allows one to restrict available commands, such as access to advanced internal commands. The [[Bourne shell]] and workalikes such as [[Bash (Unix shell)\|Bash]] can be run as a [[restricted shell]]; among other things, this prohibits the user from modifying the PATH environment variable, so that if PATH is set to include only directories that contain only permissible commands, the user will only be able to run those commands. The Windows [[CMD.EXE]] also supports restricting available commands. Often, shareware programs will limit the range of commands, including printing a command 'your administrator has disabled running batch files' from the prompt.{{Clarify\|reason=The sentence seems ambigious and confuses me. Does "including printing a command 'your administrator has disabled running batch files' from the prompt" describe an act of limiting the range of commands, or does it rather describe a command that a user may (try to) give which is then limited?\|date=July 2021}}

	Some CLIs, such as those in [[network router]]s, have a hierarchy of [[mode (user interface)\|mode]]s, with a different set of commands supported in each mode. The set of commands are grouped by association with security, system, interface, etc. In these systems the user might traverse through a series of sub-modes. For example, if the CLI had two modes called ''interface'' and ''system'', the user might use the command ''interface'' to enter the interface mode. At this point, commands from the system mode may not be accessible until the user exits the interface mode and enters the system mode.		Some CLIs, such as those in [[network router]]s, have a hierarchy of [[mode (user interface)\|mode]]s, with a different set of commands supported in each mode. The set of commands are grouped by association with security, system, interface, etc. In these systems the user might traverse through a series of sub-modes. For example, if the CLI had two modes called ''interface'' and ''system'', the user might use the command ''interface'' to enter the interface mode. At this point, commands from the system mode may not be accessible until the user exits the interface mode and enters the system mode.

Guy Harris: Consistently speak of a CLI or GUI - "interface" is a countable noun.

2025-05-22T19:57:51Z

Consistently speak of *a* CLI or GUI - "interface" is a countable noun.

← Previous revision		Revision as of 19:57, 22 May 2025
Line 6:		Line 6:
	A '''command-line interface''' ('''CLI''') is a means of interacting with [[software]] via [[command (computing)\|commands]] {{endash}} each formatted as a line of text. Command-line interfaces emerged in the mid-1960s, on [[computer terminal]]s, as an interactive and more user-friendly alternative to the non-interactive mode available with [[punched cards]].<ref>{{Cite web \|title=The evolution of command line interface (CLI): A historical insight {{!}} Contentstack \|url=https://www.contentstack.com/blog/tech-talk/the-evolution-of-command-line-interface-cli-a-historical-insight \|access-date=2025-01-28 \|website=www.contentstack.com \|language=en}}</ref>		A '''command-line interface''' ('''CLI''') is a means of interacting with [[software]] via [[command (computing)\|commands]] {{endash}} each formatted as a line of text. Command-line interfaces emerged in the mid-1960s, on [[computer terminal]]s, as an interactive and more user-friendly alternative to the non-interactive mode available with [[punched cards]].<ref>{{Cite web \|title=The evolution of command line interface (CLI): A historical insight {{!}} Contentstack \|url=https://www.contentstack.com/blog/tech-talk/the-evolution-of-command-line-interface-cli-a-historical-insight \|access-date=2025-01-28 \|website=www.contentstack.com \|language=en}}</ref>

	For a long time, CLI was the most common interface for software, but today ~~the~~ [[graphical user interface]] (GUI) is more common. None-the-less, many programs such as [[operating system]] and [[software development]] [[utility software\|utilities]] still provide CLI.		For a long time, a CLI was the most common interface for software, but today a [[graphical user interface]] (GUI) is more common. None-the-less, many programs such as [[operating system]] and [[software development]] [[utility software\|utilities]] still provide CLI.

	CLI enables [[automation\|automating]] [[computer program\|programs]] since commands can be stored in a [[scripting language\|script]] [[computer file\|file]] that can be used repeatedly. A script allows its contained commands to be executed as group; as a program; as a command.		A CLI enables [[automation\|automating]] [[computer program\|programs]] since commands can be stored in a [[scripting language\|script]] [[computer file\|file]] that can be used repeatedly. A script allows its contained commands to be executed as group; as a program; as a command.

	CLI is made possible by '''command-line interpreters''' or '''command-line processors''', which are programs that execute input commands.		A CLI is made possible by '''command-line interpreters''' or '''command-line processors''', which are programs that execute input commands.

	Alternatives to CLI include GUI (including the [[desktop metaphor]] such as [[Windows]]), [[text-based user interface\|text-based]] [[Menu (computing)\|menuing]] (including [[DOS Shell]] and [[IBM AIX SMIT]]), and [[keyboard shortcut]]s.		Alternatives to a CLI include a GUI (including the [[desktop metaphor]] such as [[Windows]]), [[text-based user interface\|text-based]] [[Menu (computing)\|menuing]] (including [[DOS Shell]] and [[IBM AIX SMIT]]), and [[keyboard shortcut]]s.

	== Comparison to graphical user interfaces ==		== Comparison to graphical user interfaces ==

Explicit: Removing link(s) Wikipedia:Articles for deletion/Nushell closed as delete (XFDcloser)

2025-05-12T00:05:27Z

Removing link(s) Wikipedia:Articles for deletion/Nushell closed as delete (XFDcloser)

← Previous revision		Revision as of 00:05, 12 May 2025
Line 24:		Line 24:
	Operating system (OS) command-line interfaces are usually distinct programs supplied with the operating system. A program that implements such a text interface is often called a command-line interpreter, command processor or [[shell (computing)\|shell]].		Operating system (OS) command-line interfaces are usually distinct programs supplied with the operating system. A program that implements such a text interface is often called a command-line interpreter, command processor or [[shell (computing)\|shell]].

	Examples of command-line interpreters include [[Nushell]], [[Digital Equipment Corporation\|DEC's]] [[DIGITAL Command Language]] (DCL) in [[OpenVMS]] and [[RSX-11]], the various [[Unix shell]]s ([[Bourne shell\|sh]], [[KornShell\|ksh]], [[C shell\|csh]], [[tcsh]], [[zsh]], [[Bash (Unix shell)\|Bash]], etc.), [[CP/M]]'s [[Console Command Processor\|CCP]], [[DOS]]' [[COMMAND.COM]], as well as the [[OS/2]] and the Windows [[CMD.EXE]] programs, the latter groups being based heavily on DEC's RSX-11 and [[RSTS/E\|RSTS]] CLIs. Under most operating systems, it is possible to replace the default shell program with alternatives; examples include [[4DOS]] for DOS, [[4OS2]] for OS/2, and [[Take Command Console\|4NT / Take Command]] for Windows.		Examples of command-line interpreters include Nushell, [[Digital Equipment Corporation\|DEC's]] [[DIGITAL Command Language]] (DCL) in [[OpenVMS]] and [[RSX-11]], the various [[Unix shell]]s ([[Bourne shell\|sh]], [[KornShell\|ksh]], [[C shell\|csh]], [[tcsh]], [[zsh]], [[Bash (Unix shell)\|Bash]], etc.), [[CP/M]]'s [[Console Command Processor\|CCP]], [[DOS]]' [[COMMAND.COM]], as well as the [[OS/2]] and the Windows [[CMD.EXE]] programs, the latter groups being based heavily on DEC's RSX-11 and [[RSTS/E\|RSTS]] CLIs. Under most operating systems, it is possible to replace the default shell program with alternatives; examples include [[4DOS]] for DOS, [[4OS2]] for OS/2, and [[Take Command Console\|4NT / Take Command]] for Windows.

	Although the term ''shell'' is often used to describe a command-line interpreter, strictly speaking, a ''shell'' can be any program that constitutes the user interface, including fully graphically oriented ones. For example, the default Windows GUI is a shell program named [[EXPLORER.EXE]], as defined in the SHELL=EXPLORER.EXE line in the WIN.INI configuration file. These programs are shells, but not CLIs.		Although the term ''shell'' is often used to describe a command-line interpreter, strictly speaking, a ''shell'' can be any program that constitutes the user interface, including fully graphically oriented ones. For example, the default Windows GUI is a shell program named [[EXPLORER.EXE]], as defined in the SHELL=EXPLORER.EXE line in the WIN.INI configuration file. These programs are shells, but not CLIs.

Jcubic: /* Other command-line interfaces */ minor

2025-05-10T13:18:48Z

Other command-line interfaces: minor

← Previous revision		Revision as of 13:18, 10 May 2025
Line 306:		Line 306:
	Programs like BASIC, [[diskpart]], [[Edlin]], and QBASIC all provide command-line interfaces, some of which use the system shell. Basic is modeled on the default interface for 8-bit Intel computers. Calculators can be run as command-line or dialog interfaces.		Programs like BASIC, [[diskpart]], [[Edlin]], and QBASIC all provide command-line interfaces, some of which use the system shell. Basic is modeled on the default interface for 8-bit Intel computers. Calculators can be run as command-line or dialog interfaces.

	[[Emacs]] provides a command-line interface in the form of its minibuffer. Commands and arguments can be entered using Emacs standard text editing support, and output is displayed in another buffer.		[[Emacs]] provides a command-line interface in the form of its minibuffer. Commands and arguments can be entered using Emacs standard text editing support, and output is displayed in another buffer.

	There are a number of text mode games, like ''[[Colossal Cave Adventure\|Adventure]]'' or ''[[King's Quest#Series\|King's Quest 1-3]]'', which relied on the user typing commands at the bottom of the screen. One controls the character by typing commands like 'get ring' or 'look'. The program returns a text which describes how the character sees it, or makes the action happen. The [[text adventure]] ''[[The Hitchhiker's Guide to the Galaxy (video game)\|The Hitchhiker's Guide to the Galaxy]]'', a piece of [[interactive fiction]] based on [[Douglas Adams\|Douglas Adam's]] book of the same name, is a teletype-style command-line game.		There are a number of text mode games, like ''[[Colossal Cave Adventure\|Adventure]]'' or ''[[King's Quest#Series\|King's Quest 1-3]]'', which relied on the user typing commands at the bottom of the screen. One controls the character by typing commands like 'get ring' or 'look'. The program returns a text which describes how the character sees it, or makes the action happen. The [[text adventure]] ''[[The Hitchhiker's Guide to the Galaxy (video game)\|The Hitchhiker's Guide to the Galaxy]]'', a piece of [[interactive fiction]] based on [[Douglas Adams\|Douglas Adam's]] book of the same name, is a teletype-style command-line game.
Line 318:		Line 318:
	A web browser's URL input field can be used as a command line. It can be used to ''launch'' [[web app]]s, [[about:config\|access browser configuration]], as well as perform a search. [[Google]], which has been called "the command line of the internet" will perform a domain-specific search when it detects search parameters in a known format.<ref name="Google"/> This functionality is present whether the search is triggered from a browser field or on Google's website.		A web browser's URL input field can be used as a command line. It can be used to ''launch'' [[web app]]s, [[about:config\|access browser configuration]], as well as perform a search. [[Google]], which has been called "the command line of the internet" will perform a domain-specific search when it detects search parameters in a known format.<ref name="Google"/> This functionality is present whether the search is triggered from a browser field or on Google's website.

	There are [[JavaScript]] libraries that allow to write command line applications in browser as standalone Web apps or as part of bigger application.<ref>{{Cite web \|url=https://terminal.jcubic.pl/ \|title=jQuery Terminal Emulator \|access-date=2021-04-20 \|archive-date=2021-04-20 \|archive-url=https://web.archive.org/web/20210420221405/https://terminal.jcubic.pl/ \|url-status=live }}</ref> An example of such a website is the CLI interface to [[DuckDuckGo]].<ref>{{Cite web \|url=https://duckduckgo.com/tty/ \|title=DuckDuckGo TTY \|access-date=2021-04-20 \|archive-date=2021-05-07 \|archive-url=https://web.archive.org/web/20210507211818/https://duckduckgo.com/tty/ \|url-status=live }}</ref> There are also [[~~Web~~-based SSH]] applications, that allow ~~to give~~ access to ~~server~~ command line interface from a browser.		There are [[JavaScript]] libraries that allow to write command line applications in browser as standalone Web apps or as part of bigger application.<ref>{{Cite web \|url=https://terminal.jcubic.pl/ \|title=jQuery Terminal Emulator \|access-date=2021-04-20 \|archive-date=2021-04-20 \|archive-url=https://web.archive.org/web/20210420221405/https://terminal.jcubic.pl/ \|url-status=live }}</ref> An example of such a website is the CLI interface to [[DuckDuckGo]].<ref>{{Cite web \|url=https://duckduckgo.com/tty/ \|title=DuckDuckGo TTY \|access-date=2021-04-20 \|archive-date=2021-05-07 \|archive-url=https://web.archive.org/web/20210507211818/https://duckduckgo.com/tty/ \|url-status=live }}</ref> There are also [[web-based SSH]] applications that allow access to a server’s command-line interface from a browser.

	Many PC [[video games]] feature a command line interface often referred to as a console. It is typically used by the game developers during development and by mod developers for debugging purposes as well as for cheating or skipping parts of the game.		Many PC [[video games]] feature a command line interface often referred to as a console. It is typically used by the game developers during development and by mod developers for debugging purposes as well as for cheating or skipping parts of the game.

Kankachi1980Kan: /* External links */

2025-05-10T03:20:13Z

External links

← Previous revision		Revision as of 03:20, 10 May 2025
Line 381:		Line 381:
	==External links==		==External links==
	* [http://www.patersontech.com/Dos/Softalk/Softalk.html The Roots of DOS] David Hunter, ''Softalk for the IBM Personal Computer'' March 1983. Archived at Patersontech.com since [https://web.archive.org/web/20001003150623/http://www.patersontech.com/Dos/Softalk/Softalk.html 2000].		* [http://www.patersontech.com/Dos/Softalk/Softalk.html The Roots of DOS] David Hunter, ''Softalk for the IBM Personal Computer'' March 1983. Archived at Patersontech.com since [https://web.archive.org/web/20001003150623/http://www.patersontech.com/Dos/Softalk/Softalk.html 2000].
	* [https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/windows-commands ~~Command-Line~~ ~~Reference~~]: Microsoft TechNet Database "Command-Line Reference"		* [https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/windows-commands Windows Commands]: Microsoft TechNet Database "Command-Line Reference"

	{{Operating system\|state=collapsed}}		{{Operating system\|state=collapsed}}

Sapphirefigure: /* Anatomy of a shell CLI */ Fixed typo

2025-05-05T11:59:38Z

Anatomy of a shell CLI: Fixed typo

← Previous revision		Revision as of 11:59, 5 May 2025
Line 70:		Line 70:

	* [[#Command prompt\|prompt]] — output by the program to indicate that its ready for input; a prompt may include contextual information and often ends with a symbol that provides a visual cue that input is expected		* [[#Command prompt\|prompt]] — output by the program to indicate that its ready for input; a prompt may include contextual information and often ends with a symbol that provides a visual cue that input is expected
	* command — input by the user, ~~aommand~~ is usually one of two classes:		* command — input by the user, a command is usually one of two classes:
	*# ''Internal'' commands are recognized and processed by the command line interpreter. Internal commands are also called built-in commands.<ref>{{Cite web \|date=2023-07-05 \|title=Shell Built-in Commands List \|url=https://linuxhandbook.com/shell-builtin-commands/ \|access-date=2024-08-05 \|website=Linux Handbook \|language=en}}</ref>		*# ''Internal'' commands are recognized and processed by the command line interpreter. Internal commands are also called built-in commands.<ref>{{Cite web \|date=2023-07-05 \|title=Shell Built-in Commands List \|url=https://linuxhandbook.com/shell-builtin-commands/ \|access-date=2024-08-05 \|website=Linux Handbook \|language=en}}</ref>
	*# ''External'' commands run executables found in separate executable files. The command line interpreter searches for executable files with names matching the external command.<ref>{{Cite web \|last=B \|first=Jason \|title=How to set your $PATH variable in Linux {{!}} Opensource.com \|url=https://opensource.com/article/17/6/set-path-linux \|access-date=2024-08-05 \|website=opensource.com \|language=en}}</ref><ref>{{Cite web \|last=JasonGerend \|date=2023-02-03 \|title=path \|url=https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/path \|access-date=2024-08-05 \|website=learn.microsoft.com \|language=en-us}}</ref>		*# ''External'' commands run executables found in separate executable files. The command line interpreter searches for executable files with names matching the external command.<ref>{{Cite web \|last=B \|first=Jason \|title=How to set your $PATH variable in Linux {{!}} Opensource.com \|url=https://opensource.com/article/17/6/set-path-linux \|access-date=2024-08-05 \|website=opensource.com \|language=en}}</ref><ref>{{Cite web \|last=JasonGerend \|date=2023-02-03 \|title=path \|url=https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/path \|access-date=2024-08-05 \|website=learn.microsoft.com \|language=en-us}}</ref>

← Previous revision		Revision as of 12:59, 13 June 2025
Line 6:		Line 6:
	A '''command-line interface''' ('''CLI''') is a means of interacting with [[software]] via [[command (computing)\|commands]] {{endash}} each formatted as a line of text. Command-line interfaces emerged in the mid-1960s, on [[computer terminal]]s, as an interactive and more user-friendly alternative to the non-interactive mode available with [[punched cards]].<ref>{{Cite web \|title=The evolution of command line interface (CLI): A historical insight {{!}} Contentstack \|url=https://www.contentstack.com/blog/tech-talk/the-evolution-of-command-line-interface-cli-a-historical-insight \|access-date=2025-01-28 \|website=www.contentstack.com \|language=en}}</ref>		A '''command-line interface''' ('''CLI''') is a means of interacting with [[software]] via [[command (computing)\|commands]] {{endash}} each formatted as a line of text. Command-line interfaces emerged in the mid-1960s, on [[computer terminal]]s, as an interactive and more user-friendly alternative to the non-interactive mode available with [[punched cards]].<ref>{{Cite web \|title=The evolution of command line interface (CLI): A historical insight {{!}} Contentstack \|url=https://www.contentstack.com/blog/tech-talk/the-evolution-of-command-line-interface-cli-a-historical-insight \|access-date=2025-01-28 \|website=www.contentstack.com \|language=en}}</ref>

	For a long time, a CLI was the most common interface for software, but today a [[graphical user interface]] (GUI) is more common. ~~None-the-less~~, many programs such as [[operating system]] and [[software development]] [[utility software\|utilities]] still provide CLI.		For a long time, a CLI was the most common interface for software, but today a [[graphical user interface]] (GUI) is more common. Nonetheless, many programs such as [[operating system]] and [[software development]] [[utility software\|utilities]] still provide CLI.

	A CLI enables [[automation\|automating]] [[computer program\|programs]] since commands can be stored in a [[scripting language\|script]] [[computer file\|file]] that can be used repeatedly. A script allows its contained commands to be executed as group; as a program; as a command.		A CLI enables [[automation\|automating]] [[computer program\|programs]] since commands can be stored in a [[scripting language\|script]] [[computer file\|file]] that can be used repeatedly. A script allows its contained commands to be executed as group; as a program; as a command.

← Previous revision		Revision as of 11:52, 23 May 2025
Line 356:		Line 356:
	<ref name="Kerninghan_1984">{{cite book \|author-first1=Brian W. \|author-last1=Kernighan \|author-link1=Brian Kernighan \|author-first2=Rob \|author-last2=Pike \|author-link2=Rob Pike \|title=The UNIX Programming Environment \|location=Englewood Cliffs \|publisher=[[Prentice-Hall]] \|date=1984 \|isbn=0-13-937699-2 \|url=https://archive.org/details/unixprogramminge0000kern \|url-access=registration}}</ref>		<ref name="Kerninghan_1984">{{cite book \|author-first1=Brian W. \|author-last1=Kernighan \|author-link1=Brian Kernighan \|author-first2=Rob \|author-last2=Pike \|author-link2=Rob Pike \|title=The UNIX Programming Environment \|location=Englewood Cliffs \|publisher=[[Prentice-Hall]] \|date=1984 \|isbn=0-13-937699-2 \|url=https://archive.org/details/unixprogramminge0000kern \|url-access=registration}}</ref>
	<ref name="Pouzin">{{cite web \|author-last=Pouzin \|author-first=Louis \|title=The Origin of the Shell \|work=Multicians.org \|url=http://www.multicians.org/shell.html \|access-date=2013-09-22 \|archive-date=2017-12-21 \|archive-url=https://web.archive.org/web/20171221142542/http://www.multicians.org/shell.html \|url-status=live }}</ref>		<ref name="Pouzin">{{cite web \|author-last=Pouzin \|author-first=Louis \|title=The Origin of the Shell \|work=Multicians.org \|url=http://www.multicians.org/shell.html \|access-date=2013-09-22 \|archive-date=2017-12-21 \|archive-url=https://web.archive.org/web/20171221142542/http://www.multicians.org/shell.html \|url-status=live }}</ref>
	<ref name="Betanews">{{cite web\|title=Remembering Windows 95's launch 15 years later\|date=24 August 2010\|url=http://betanews.com/2010/08/24/remembering-windows-95-s-launch-15-years-later/\|access-date=2015-02-18 \|archive-date=2015-02-18 \|archive-url=https://web.archive.org/web/20150218221032/http://betanews.com/2010/08/24/remembering-windows-95-s-launch-15-years-later/\|url-status=live}}</ref>		<ref name="Betanews">{{cite web\|author-first1=Joe\|author-last1=Wilcox\|website=BetaNews\|title=Remembering Windows 95's launch 15 years later\|date=24 August 2010\|url=http://betanews.com/2010/08/24/remembering-windows-95-s-launch-15-years-later/\|access-date=2015-02-18 \|archive-date=2015-02-18 \|archive-url=https://web.archive.org/web/20150218221032/http://betanews.com/2010/08/24/remembering-windows-95-s-launch-15-years-later/\|url-status=live}}</ref>
	<ref name="Microsoft_History">{{cite web \|title=A history of Windows \|website=windows.microsoft.com \|url=http://windows.microsoft.com/en-US/windows/history#T1=era0 \|archive-url=https://web.archive.org/web/20150301073112/http://windows.microsoft.com/en-US/windows/history \|archive-date=2015-03-01}}</ref>		<ref name="Microsoft_History">{{cite web \|title=A history of Windows \|website=windows.microsoft.com \|url=http://windows.microsoft.com/en-US/windows/history#T1=era0 \|archive-url=https://web.archive.org/web/20150301073112/http://windows.microsoft.com/en-US/windows/history \|archive-date=2015-03-01}}</ref>
	<ref name="Microsoft_POSIX">{{cite web \|title=Windows POSIX shell compatibility \|date=22 February 2013 \|url=https://technet.microsoft.com/en-us/library/cc754351.aspx \|access-date=2017-08-26 \|archive-date=2017-07-03 \|archive-url=https://web.archive.org/web/20170703090254/https://technet.microsoft.com/en-us/library/cc754351.aspx \|url-status=live }}</ref>		<ref name="Microsoft_POSIX">{{cite web \|title=Windows POSIX shell compatibility \|date=22 February 2013 \|url=https://technet.microsoft.com/en-us/library/cc754351.aspx \|access-date=2017-08-26 \|archive-date=2017-07-03 \|archive-url=https://web.archive.org/web/20170703090254/https://technet.microsoft.com/en-us/library/cc754351.aspx \|url-status=live }}</ref>