Lines Matching full:commands

41 directory and begins by reading commands from a file
46 We will later see what kinds of commands are usefully placed there.
53 will, after it reads commands from
55 read commands from a file
58 This file contains commands which you wish to do each time you log in
77 This file contains several commands to be executed by UNIX
114 print out statistics lines for commands which execute for at least 15 seconds
116 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'.
198 Other commands may live in /bin and /usr/bin.
223 which you insert into your path and determines which commands are contained
225 this means that if commands are added to a directory in your search path after
309 of previous commands.
310 It is possible to use a notation to reuse commands or words
311 from commands in forming new commands.
312 This mechanism can be used to repeat previous commands or to
313 correct minor typing mistakes in commands.
385 commands starting with `c' done recently we could have said `!cc' or even
394 may be used anywhere in the formation of new commands and other characters
395 may be placed before and after the substituted commands.
410 There are other mechanisms available for repeating commands.  The
412 command prints out a number of previous commands with numbers by which
423 mechanism which can be used to make transformations on input commands.
424 This mechanism can be used to simplify the commands you type,
425 to supply default arguments to commands,
426 or to perform transformations on commands and their arguments.
431 or involve commands such as
473 mechanism can be used to provide short names for commands,
475 and to define new short commands in terms of other commands.
477 commands or pipelines, showing where the arguments to the original
497 The `;' separating commands is used here
508 file each time it starts up.  If you place a large number of commands
514 the system seem sluggish when you execute commands from within the editor
522 In addition to the standard output, commands also have a
581 When one or more commands
582 are typed together as a pipeline or as a sequence of commands separated by
585 is created by the shell consisting of these commands together as a unit.
586 Single commands without pipes or semicolons create the simplest jobs.
596 at the end of the commands, then the job is started as a
617 until it finished, even though you can type and execute more commands in the
658 of all commands in the job, as well as the working directory where the job was
671 which can be used later to refer to the job in the commands described below.
676 as the process numbers of all its (top level) commands, is typed by the shell
725 change what you are doing (execute other commands) and then return to
740 it in the background allowing more foreground commands to be executed.
747 commands can take an argument that identifies a particular
750 job control commands also accept process numbers (printed by the
776 commands and status (`Suspended' or `Running') of each background or
858  . . .  some foreground commands
878 accept commands from the terminal.
1122 Useful built-in commands
1124 We now give a few of the useful built-in commands of the shell describing
1194 command causes the shell to recompute a table of where commands are
1239 command can be used to force the current shell to read commands from
1284 commands can be used