Lines Matching full:shell

31 Details on the shell for terminal users
33 Shell startup and termination
35 When you login, the shell is started by the system in your
43 For now we need not have this file and the shell does not complain about
47 .I "login shell" ,
78 command which is interpreted directly by the shell.  It sets the shell
81 which causes the shell to not log me off if I hit ^D.  Rather,
87 variable, I ask the shell to watch for incoming mail to me.  Every 5 minutes
88 the shell looks for this file and tells me if more mail has arrived there.
98 Next I set the shell variable `time' to `15' causing the shell to automatically
101 I want the shell to remember the last 10 commands I type in its
123 When the `mail' and `msgs' programs finish, the shell will finish
130 command) the shell
133 After that the shell will terminate and \s-2UNIX\s0 will log
136 In any case, after the `logout' message the shell is committed to terminating
139 Shell variables
141 The shell maintains a set of
148 In fact, each shell variable has as value an array of
151 Shell variables may be assigned values by the set command.  It has
157 Shell variables may be used to store values which are to
159 The shell variables most commonly referenced are, however, those which the
160 shell itself refers to.
162 behavior of the shell.
166 This variable contains a sequence of directory names where the shell
173 in the shell.
185 shell	/bin/csh
221 One thing you should be aware of is that the shell examines each directory
223 there.  Except for the current directory `.', which the shell treats specially,
225 you have started the shell, they will not necessarily be found by the shell.
231 to the shell, which will cause it to recompute its internal table of command
233 Since the shell has to look in the current directory `.' on each command,
246 file to tell the shell not to exit when it receives an end-of-file from
249 is one of several variables which the shell does not care about the
264 Finally, some other built-in shell variables of use are the
276 If you would prefer that the shell not overwrite files in this
303 The shell's history list
305 The shell can maintain a
315 history mechanism of the shell.
377 The shell echoed the command, as it would have been typed without use of
403 we used a shell substitute, placing the old text and new text between `^'
415 is given in the C shell manual pages in the \s-2UNIX\s0 Programmer's Manual.
419 The shell has an
427 using shell command files, but these take place in another instance
428 of the shell and cannot directly affect the current shells environment
431 which must be done in the current shell.
437 If you place the shell command
443 file, the shell will transform an input line of the form
464 then the shell will translate this to
504 The shell currently reads the
507 there, shells will tend to start slowly.  A mechanism for saving the shell
532 The `>&' here tells the shell to route both the diagnostic output and the
564 does not exist, otherwise the shell will create
583 is created by the shell consisting of these commands together as a unit.
585 Usually, every line typed to the shell creates a job.
596 job.  This means that the shell does not wait for it to complete but
601 jobs, continue to be read and executed by the shell one at a time.
618 job terminates, a message is typed by the shell just before the next prompt
653 Jobs are recorded in a table inside the shell until they terminate.
654 In this table, the shell remembers the command names, arguments and the
660 with the shell waiting for it to terminate, running
674 as the process numbers of all its (top level) commands, is typed by the shell
686 together as a background job.  After starting the job, the shell prints
688 of each program started in the job.  Then the shell immediates prompts for
699 or the background.  The shell notices when a job becomes stopped and
708 `Stopped' message is typed by the shell when it notices that the
930 command only prints jobs started in the currently executing shell,
932 or within shell files.  The
935 in the current shell.
939 As mentioned in section 1.6, the shell is always in a particular
947 changes the working directory of the shell,
959 reports the absolute pathname of the working directory of the shell,
989 changes the shell's working directory to the one directly above the
1004 The shell always remembers the pathname of its current working directory in
1007 The shell can also be requested to remember the previous directory when
1012 command, the shell saves the name of the current working directory
1072 Since the shell remembers the working directory in which each job
1075 current working directory of the shell.  Thus if you start a background
1076 job, then change the shell's working directory and then cause the
1077 background job to run in the foreground, the shell warns you that the
1079 from that of the shell.
1097 This way the shell warns you when there
1100 even though the shell had changed to `/mnt/bill'.
1103 the return to the shell again implies a change of working directory.
1113 their own working directories, since the shell only remembers which
1119 from the current working directory of the shell.
1123 We now give a few of the useful built-in commands of the shell describing
1141 .I "shell scripts"
1151 There is also a shell variable called
1153 By placing a `!' character in its value the shell will there substitute
1187 command can be used to terminate a login shell which has
1193 command causes the shell to recompute a table of where commands are
1195 in the current shell's search path and wish the shell to find it,
1196 since otherwise the hashing algorithm may tell the shell that the
1229 SHELL=/bin/csh
1238 command can be used to force the current shell to read commands from
1284 to remove aliases and variable definitions from the shell, and
1290 This concludes the basic discussion of the shell for terminal users.
1291 There are more features of the shell to be discussed here, and all
1292 features of the shell are discussed in its manual pages.