This guideline is a part of the English Wikipedia's Manual of Style. Editors should follow it, except where common sense and the occasional exception will improve an article. Before editing this page, please make sure that your revision reflects consensus.

Shortcut: WP:MOSCOMM

Style and formatting
Manual of Style and its subpages
Abbreviations Accessibility Anime & manga articles Biographies Capital letters Chemistry Command-line examples Dates and numbers Disambiguation pages Flags & similar icons Infoboxes Legal Links Lists of works Mathematics Medicine Military history guidelines Music Pronunciation Spelling Text formatting Titles Trademarks Writing about fiction
Related policies and guidelines
Captions Categorization Categorization of people Citing sources Explain jargon External links Film guidelines Footnotes Layout Lead section Lists Music samples Naming conventions Overlinking Proper names Stubs Summary style Technical terms Trivia sections Writing better articles Wikimedia sister projects Words to avoid
Related help, tutorials and proposals
Glossary How to edit a page Picture tutorial Sections
Related to specific cultures
Arabic-related articles Chinese language Chinese history Ethiopia-related articles France & French-related Hebrew transliteration India-related articles Ireland-related articles Islam-related articles Japan-related articles Korea-related articles Latter Day Saints Philippines-related articles Portugal-related articles Thailand-related articles Syriac/Assyrian-related articles United Kingdom nationalities U.S. highways

Command-line examples are used to specify the syntax of shell commands or programs as a user would type them into a terminal or command prompt on a computer. This page is intended to function as a style guide for writers and editors of articles related to computer science on Wikipedia.

General guidelines

When providing command-line examples, it is necessary to maintain clarity and simplicity. Not only does this result in a more professional look, but it prevents the reader from becoming confused. The following guidelines are given to help establish what defines clear and simple examples.

• Command-line examples should be presented in a monospaced font. The initial presentation should use the Wikipedia method that involves prefixing commands with a space. Further references should be contained in <tt> (teletype) tags.
• Wikipedia is not a medium for the presentation of writers' personal preferences. As such, there should not be any reference to environment, date, working directory, user name, or host name unless absolutely necessary.
• Terminology: An option is a switch (something that modifies the general behavior of the command). A parameter is a specific value, such as a file or host name. The term argument is used to refer to any of the space-separated strings that follow a command name, including both options and parameters.
• When presenting arguments, care should be taken to maintain simplicity. Specifying them without explanation can confuse the reader.
• Wikipedia is not a substitute for manual pages. Articles should not document the entire list of options associated with a command unless there are very few such options or such descriptiveness is absolutely necessary.
• When specifying parameters, logical names should be used to refer to them. These names should be italicised and should not contain spaces, as spaces are used to separate multiple arguments on the command line. The following are some examples:

(prompt) command parameter-name

(prompt) command parameterName

(prompt) command parameter_name

(prompt) command parametername

• Consistency is important. Do not confuse the reader by using all four methods of naming parameters in the same article.
• Arguments that are not required and may be completely omitted should be enclosed within square brackets, and .
• There are many ways of specifying repeating parameters; the following two are the most common:

(prompt) command parameter0 [.. parameterN

(prompt) command parameter ...]

Platform-specific guidelines

DOS, Microsoft Windows, and OS/2

The most common operating system in use today is Microsoft Windows, whose command-line syntax is based on that of MS-DOS. As such, examples that might be specific to MS-DOS or Windows do not need to indicate this. However, if the examples are specific to a certain version of the operating system, then they should be indicated as such. If equivalents in other DOSes differ and are known, they should be provided.

The following additional guidelines should be followed for DOS command-line examples:

• The names of commands and programs should be provided in all upper-case letters.
• Standard MS-DOS–style options (of the form /C where C is some character) should also be upper-case, unless they are case sensitive.
• Program names should be contrasted against built-in command names by appending their appropriate file extension. If a specific program is not included with certain versions of MS-DOS (such as MOVE.EXE or EDIT.COM), then the versions for which it is known to be included should be indicated.

Unix-like systems

• Most commands on Unix-like systems are actually references to executable files. Commands that are native to a shell (such as cd or history) should be indicated as such.
• The most common shell on Unix-like systems has varied greatly. As a result, shell-specific commands or utilities (such as the for loop or certain stream behaviors) should be avoided whenever possible.
• If a shell-specific sequence is required for proper explanation, then an example should be provided for both the ALGOL-like sequence of sh, ksh, and bash as well as one for the C-like syntax of csh and tcsh. This is not necessary if there is no difference in the syntax.
• The names of most commands on Unix-like systems are made up of all lower-case characters. However, due to the case-sensitive nature of the shell and operating environment, care should be taken to ensure that the capitalisation given matches that of the command or file name. Use of the wrongtitle template is recommended as well when necessary.
• Commands that normally require privileged access should be differentiated from those that do not require it.
• In some cases, it is very likely the value of a parameter will contain some shell metacharacters. In these cases, it may be wise to specify quoting in the example to prevent users from receiving errors that to them will seem strange and unrelated.

Providing sample output

It may often be prudent to provide a sample of the output that a command is expected to generate. In these cases, the full command and all arguments as they were typed are given. The output of the command will therefore be specific to environment and other variables. The tags <pre><nowiki> (in that order) will insure the proper formatting of the output.

Examples of usage

DOS

• The DIR built-in command on DOS, which lists files and directories:

> DIR options pattern ...]

• The program MOVE.EXE on MS-DOS (whose behavior had to be emulated prior to its introduction):

> MOVE.EXE source target

General Unix

• The ls command on Unix-like systems, which lists files and directories:

$ ls options file ...]

• The mkfs command, which creates new file systems and as such usually requires privileged access:

# mkfs [-t fstype fs-options device

• The wget program, one of the GNU utilities, which retrieves files given a Uniform Resource Identifier (URI). URIs can sometimes contain shell meta-characters, and so the parameter is quoted to prevent errors.

$ wget options "URI"

Shell-specific

• The if built-in structure, whose syntax differs between sh/ksh/bash:

$ if command ; then command ; ... ; fi

and csh/tcsh:

% if (expression) then command ; ... ; endif

Sample output

• Sample output of the df command, which lists disk space usage on mounted file systems:

$ df -P
Filesystem          512-blocks      Used Available Capacity Mounted on
/dev/hda2             39331760   7398904  29834768      20% /