Command line psychology 101

One of the mysteries of Unix (aside from Unix itself) is the command line, filled as it is with strange and cryptic characters. Now let's see, do I need a dot between two backslashes, or should it be a backwards quote followed by a hyphen?

One thing that will help sort out what is actually happening in a command line, and maybe even help you construct one of your own, is an understanding of how the command line is interpreted.

The command line is actually the input to the shell program. The shell program (sh, ksh, csh, or any other variant) reads the input line and untangles it before it attempts to execute the command. The sequence of steps the program goes through to untangle a command provides interesting insight into shell programming. By studying it you're sure to learn some new tricks.

We will cover these pieces in more detail in a moment, but first let's take a look at the sequence of evaluation of a command line:

1. History substitution (except for the Bourne shell)
2. Splitting words, including special characters
3. Updating the history list (except for the Bourne shell)
4. Interpreting single and double quotes
5. Alias substitution (except for the Bourne shell)
6. Redirection of input and output (< > and |)
7. Variable substitution (variables starting with $)
8. Command substitution (commands inside back quotes)
9. File name expansion (file name wild cards)

You will note that the Bourne shell is missing the steps to do with history and alias substitution. These are not included in the Bourne shell.

History substitution

If you have history set up in the Korn shell (ksh), C shell (csh), or any similar shell, command lines are saved in a history file before they are executed. You can review your previous commands by typing:

$ history

The list of commands is preceded by a number, as in:

13 ls *.txt
14 cd $HOME
15 ls *.log

In Korn shell you can usually recover a history command by typing r followed by the number. For example, typing r 13 in the example above would repeat the command ls *.txt.

In the C shell, use an exclamation point and no space instead of an r: !13.

Sign up for ITworld's Daily newsletter
Follow ITworld on Twitter @IT_world

• Email
• Print
• Share
  • Slashdot
  • Digg
  • Stumble
  • Reddit
  • Newsvine