Lines Matching +full:working +full:- +full:directory

1 .\"-
37 directory and begins by reading commands from a file
39 in this directory.
53 also in your home directory.
55 to the \s-2UNIX\s0 system.
64 \'set noglob ; eval \`tset \-s \-m dialup:c100rv4pna \-m plugboard:?hp2621nl \!*\`\';
67 msgs \-f
68 if (\-e $mail) then
74 This file contains several commands to be executed by \s-2UNIX\s0
100 of \s-2CPU\s+2 time. The variable `history' is set to 10 indicating that
118 system messages which I have not seen before; the `\-f' option here prevents
132 if it exists in my home directory.
133 After that the shell will terminate and \s-2UNIX\s0 will log
166 This variable contains a sequence of directory names where the shell
193 directory `.' and then `/usr/ucb', `/bin' and `/usr/bin'.
199 A number of locally developed programs on the system live in the directory
208 in our home directory.
217 Another directory that might interest you is /usr/new, which contains
218 many useful user-contributed programs provided with Berkeley Unix.
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,
224 this means that if commands are added to a directory in your search path after
233 Since the shell has to look in the current directory `.' on each command,
239 which shows your home directory,
241 which contains your current working directory,
246 file to tell the shell not to exit when it receives an end-of-file from
264 Finally, some other built-in shell variables of use are the
347 % !c \-o bug
348 cc bug.c \-o bug
352 % ls \-l !*
353 ls \-l a.out bug
390 an extra `\-o bug' telling the compiler to place the resultant binary in
396 we have created were, and then an `ls \-l' command with the same argument
415 is given in the C shell manual pages in the \s-2UNIX\s0 Programmer's Manual.
449 sizes of files, that is to always do `\-s'.
452 alias ls ls \-s
456 alias dir ls \-s
459 which does an `ls \-s'.
466 ls \-s /mnt/bill
484 command after each change directory
492 The `\e!*' here substitutes the entire argument list to the pre-aliasing
589 ls \-s | sort \-n | head \-5
608 program, which reports on the disk usage of your working directory (as well as
636 [1] \- Done du > usage
651 the \s-2STOP\s0, \s-2INTERRUPT\s0, or \s-2QUIT\s0 signals mentioned earlier.
656 of all commands in the job as well as the working directory where the job was
671 the same until the job terminates and then are re-used.
678 % ls \-s | sort \-n > usage &
682 runs the `ls' program with the `\-s' options, pipes this output into
683 the `sort' program with the `\-n' option which puts its output into the
694 which sends a \s-2STOP\s0 signal to the currently running
763 job \- identified by a `\-' in the output of
766 When given, the argument is either `%\-' (indicating
776 suspended job. With the `\-l' option the process numbers are also
781 % ls \-s | sort \-n > myfile &
789 [2] Running ls \-s | sort \-n > myfile
792 ls \-s | sort \-n > myfile
811 \s-2STOP\s0 signal. The combination of the \s-2STOP\s0 signal and the
913 % stty \-tostop
937 Working Directories
940 .I "working directory."
941 The `change directory' command
947 changes the working directory of the shell,
948 that is, changes the directory you
951 It is useful to make a directory for each project you wish to work on
952 and to place all files related to that project in that directory.
953 The `make directory' command,
955 creates a new directory.
958 (`print working directory') command
959 reports the absolute pathname of the working directory of the shell,
960 that is, the directory you are
973 directory
978 No matter where you have moved to in a directory hierarchy,
979 you can return to your `home' login directory by doing just
984 The name `..' always means the directory above the current one in
989 changes the shell's working directory to the one directly above the
997 change to the directory `programs' contained in the directory
1000 projects under, say, your home directory,
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
1008 you change to a new working directory. If the `push directory' command
1012 command, the shell saves the name of the current working directory
1014 .I "directory stack"
1035 shorthand for your home directory\(emin this case `/usr/bill'.
1036 The directory stack is printed whenever there is more than one
1044 since it shows the current working directory as well as any
1050 alternates the current directory with the first directory in the
1052 The `pop directory'
1054 command without an argument returns you to the directory you were in prior to
1055 the current one, discarding the previous current directory from the
1067 to manipulate the contents of the directory stack and to change
1072 Since the shell remembers the working directory in which each job
1074 a job in the foreground which has a different working directory than the
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
1078 working directory of the currently running foreground job is different
1081 % dirs \-l
1098 is an implied change of working directory, even though no cd command was
1102 terminates or is suspended (using the \s-2STOP\s0 signal) since
1103 the return to the shell again implies a change of working directory.
1113 their own working directories, since the shell only remembers which
1114 directory a job is started in, and assumes it stays there.
1115 The `\-l' option of
1117 will type the working directory
1119 from the current working directory of the shell.
1121 Useful built-in commands
1123 We now give a few of the useful built-in commands of the shell describing
1194 located. This is necessary if you add a command to a directory
1197 command wasn't in that directory when the hash table was computed.
1219 will set the value of the environment variable \s-2TERM\s0
1251 \s-2CPU\s0 time it takes.
1276 the command `wc' used an average of 13 percent of the available \s-2CPU\s0
1295 built-in command which can be used to run the same command
1298 If you intend to use \s-2UNIX\s0 a lot you should look through