Differences
This shows you the differences between two versions of the page.
| en:docs:cmd:cmdline:cmd-names-and-parm [2014/05/27 07:34] – created valerius | en:docs:cmd:cmdline:cmd-names-and-parm [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== Command Names and Parameters ===== | ||
| - | |||
| - | When you enter a command you type its name at the prompt, followed by a space and any parameters for the command. For example, all of these could be valid commands: | ||
| - | |||
| - | < | ||
| - | [c:\] dir | ||
| - | [c:\] copy file1 file2 d:\ | ||
| - | [c:\] f: | ||
| - | [c:\] "c:\my programs\jp software\take command\tcmdos2.exe" | ||
| - | </ | ||
| - | |||
| - | The last three commands above include both a command name, and one or more parameters. There are no spaces within the command name (except in quoted file names), but there is a space between the command name and any parameeters, | ||
| - | |||
| - | Some commands may work when parameters are entered directly after the command (without an intervening space, //e.g.// **dir/p**), or when several parameters are entered without spaces between them (//e.g.// **dir /2/p**). A very few older programs may even require this approach. However leaving out spaces in this way is usually technically incorrect, and is not recommended as a general practice, as it may not work for all commands. | ||
| - | |||
| - | If the command name includes a path, the elements must be separated with backslashes (//e.g.// f: | ||
| - | |||
| - | For more information on command entry see [[en: | ||