Lines Matching full:commands

37 directory and begins by reading commands from a file
42 We will later see what kinds of commands are usefully placed there.
49 will, after it reads commands from
51 read commands from a file
54 This file contains commands which you wish to do each time you login
74 This file contains several commands to be executed by \s-2UNIX\s0
99 print out statistics lines for commands which execute for at least 15 seconds
101 I want the shell to remember the last 10 commands I type in its
126 file and begin reading commands from the terminal, prompting for each with
131 will print `logout' and execute commands from the file `.logout'
158 be used in commands later through a substitution mechanism.
167 searches for commands.
194 Commands which you may write might be in `.' (usually one of
196 Commands developed at Berkeley, live in `/usr/ucb'
197 while commands developed at Bell Laboratories live in `/bin' and `/usr/bin'.
222 which you insert into your path and determines which commands are contained
224 this means that if commands are added to a directory in your search path after
308 of previous commands.
309 It is possible to use a notation to reuse commands or words
310 from commands in forming new commands.
311 This mechanism can be used to repeat previous commands or to
312 correct minor typing mistakes in commands.
383 commands starting with `c' done recently we could have said `!cc' or even
392 may be used anywhere in the formation of new commands and other characters
393 may be placed before and after the substituted commands.
408 There are other mechanisms available for repeating commands.  The
410 command prints out a number of previous commands with numbers by which
421 mechanism which can be used to make transformations on input commands.
422 This mechanism can be used to simplify the commands you type,
423 to supply default arguments to commands,
424 or to perform transformations on commands and their arguments.
429 or involve commands such as
471 mechanism can be used to provide short names for commands,
473 and to define new short commands in terms of other commands.
475 commands or pipelines, showing where the arguments to the original
495 The `;' separating commands is used here
506 file each time it starts up.  If you place a large number of commands
512 the system seem sluggish when you execute commands from within the editor
520 In addition to the standard output, commands also have a
579 When one or more commands
580 are typed together as a pipeline or as a sequence of commands separated by
583 is created by the shell consisting of these commands together as a unit.
584 Single commands without pipes or semicolons create the simplest jobs.
594 at the end of the commands, then the job is started as a
615 until it finished, even though you can type and execute more commands in the
656 of all commands in the job as well as the working directory where the job was
669 which can be used later to refer to the job in the commands described below.
674 as the process numbers of all its (top level) commands, is typed by the shell
724 change what you are doing (execute other commands) and then return to
739 it in the background allowing more foreground commands to be executed.
746 commands can take an argument that identifies a particular
749 job control commands also accept process numbers (printed by the
775 commands and status (`Stopped' or `Running') of each background or
857  . . .  some foreground commands
877 accept commands from the terminal.
1121 Useful built-in commands
1123 We now give a few of the useful built-in commands of the shell describing
1193 command causes the shell to recompute a table of where commands are
1238 command can be used to force the current shell to read commands from
1283 commands can be used