-.\" $OpenBSD: csh.1,v 1.9 2004/04/21 08:11:15 jmc Exp $
+.\" $OpenBSD: csh.1,v 1.10 2010/07/22 08:30:29 jmc Exp $
.\" $NetBSD: csh.1,v 1.3 1995/03/21 09:03:33 cgd Exp $
.\"
.\" Copyright (c) 1980, 1993
.I history
mechanism similar to the
.I redo
-of \s-2INTERLISP\s0.
+of INTERLISP.
While incorporating many features of other shells which make
writing shell programs (shell scripts) easier,
most of the features unique to
.I csh
-are designed more for the interactive \s-2UNIX\s0 user.
+are designed more for the interactive UNIX user.
.PP
-\s-2UNIX\s0
+UNIX
users who have read a general introduction to the system
will find a valuable basic explanation of the shell here.
Simple terminal interaction with
is a command language interpreter.
.I Csh
is the name of one particular command interpreter on
-\s-2UNIX\s0.
+UNIX.
The primary purpose of
.I csh
is to translate command lines typed at a terminal into
Hopefully,
.I csh
will be a very useful program for you
-in interacting with the \s-2UNIX\s0 system.
+in interacting with the UNIX system.
.PP
In addition to this document, you will want to refer to a copy
-of the \s-2UNIX\s0 User Reference Manual.
+of the UNIX User Reference Manual.
The
.I csh
documentation in section 1 of the manual provides a full description of all
.I italics .
These are important words;
names of commands, and words which have special meaning in discussing
-the shell and \s-2UNIX\s0.
+the shell and UNIX.
Many of the words are defined in a glossary at the end of this document.
If you don't know what is meant by a word, you should look
for it in the glossary.
A
.I shell
in
-\s-2UNIX\s0
+UNIX
acts mostly as a medium through which other
.I programs
are invoked.
that it is used almost exclusively as a mechanism for invoking other programs.
.PP
.I Commands
-in the \s-2UNIX\s0 system consist of a list of strings or
+in the UNIX system consist of a list of strings or
.I words
interpreted as a
.I "command name"
and signaled us that it was ready to read from the terminal again by
printing another `% ' prompt.
.PP
-This is the essential pattern of all interaction with \s-2UNIX\s0
+This is the essential pattern of all interaction with UNIX
through the shell.
A complete command is typed at the terminal, the shell executes
the command and when this execution completes, it prompts for a new command.
.NH 2
Flag arguments
.PP
-A useful notion in \s-2UNIX\s0 is that of a
+A useful notion in UNIX is that of a
.I flag
argument.
While many arguments to commands specify file names or user names,
.I ls
to also give, for each file the size of the file in blocks of 512
characters.
-The manual section for each command in the \s-2UNIX\s0 reference manual
+The manual section for each command in the UNIX reference manual
gives the available options for each command.
The
.I ls
command has a large number of useful and interesting options.
Most other commands have either no options or only one or two options.
It is hard to remember options of commands which are not used very
-frequently, so most \s-2UNIX\s0 utilities perform only one or two functions
+frequently, so most UNIX utilities perform only one or two functions
rather than having a large number of hard to remember options.
.NH 2
Output to files
be a scratch file.*
.FS
*Note that if your erase character is a `#', you will have to precede the
-`#' with a `\e'. The fact that the `#' character is the old (pre-\s-2CRT\s0)
+`#' with a `\e'. The fact that the `#' character is the old (pre-CRT)
standard erase character means that it seldom appears in a file name, and
allows this convention to be used for scratch files. If you are using a
-\s-2CRT\s0, your erase character should be a ^H, as we demonstrated
+CRT, your erase character should be a ^H, as we demonstrated
in section 1.1 how this could be set up.
.FE
The system will remove such files after a couple of days,
Filenames
.PP
Many commands to be executed will need the names of files as arguments.
-\s-2UNIX\s0
+UNIX
.I pathnames
consist of a number of
.I components
on your terminal.
This is likely to continue for several minutes unless you stop it.
You can send an
-\s-2INTERRUPT\s0
+INTERRUPT
.I signal
to the
.I cat
command by typing ^C on your terminal.*
.FS
-*On some older Unix systems the \s-2DEL\s0 or \s-2RUBOUT\s0 key
+*On some older Unix systems the DEL or RUBOUT key
has the same effect. "stty all" will tell you the `intr' key value.
.FE
Since
.I cat
does not take any precautions to avoid or otherwise handle this signal,
the
-\s-2INTERRUPT\s0
+INTERRUPT
will cause it to terminate.
The shell notices that
.I cat
has terminated and prompts you again with `% '.
-If you hit \s-2INTERRUPT\s0 again, the shell will just
-repeat its prompt since it handles \s-2INTERRUPT\s0 signals
+If you hit INTERRUPT again, the shell will just
+repeat its prompt since it handles INTERRUPT signals
and chooses to continue to execute commands rather than terminating
like
.I cat
program in the first example above was terminated when we typed a ^D
which generates an end-of-file from the standard input.
The shell also terminates when it gets an end-of-file, printing `logout';
-\s-2UNIX\s0 then logs you off the system.
+UNIX then logs you off the system.
Since this means that typing too many ^D's can accidentally log us off,
the shell has a mechanism for preventing this.
This
command would have received an end-of-file from it and terminated.
Using a pipe here is more complicated than redirecting input
so we would more likely use the first form.
-These commands could also have been stopped by sending an \s-2INTERRUPT\s0.
+These commands could also have been stopped by sending an INTERRUPT.
.PP
Another possibility for stopping a command is to suspend its execution
temporarily, with the possibility of continuing execution later. This is
-done by sending a \s-2STOP\s0 signal via typing a ^Z.
+done by sending a STOP signal via typing a ^Z.
This signal causes all commands running on the terminal
(usually one, but more if a pipeline is executing) to become suspended.
The shell notices that the command(s) have been suspended, types
`Suspended', and then prompts for a new command.
The previously executing command has been suspended, but otherwise
-unaffected by the \s-2STOP\s0 signal. Any other commands can be executed
+unaffected by the STOP signal. Any other commands can be executed
while the original command remains suspended. The suspended command can
be continued using the
.I fg
command will show which commands are suspended.
The ^Z should only be typed at the beginning of a line since
everything typed on the current line is discarded when a signal is sent
-from the keyboard. This also happens on \s-2INTERRUPT\s0, and \s-2QUIT\s0
+from the keyboard. This also happens on INTERRUPT, and QUIT
signals. More information on
suspending jobs and controlling them is given in
section 2.6.
.PP
If you write or run programs which are not fully debugged, then it may
be necessary to stop them somewhat ungracefully.
-This can be done by sending them a \s-2QUIT\s0
+This can be done by sending them a QUIT
signal, sent by typing a ^\e.
This will usually provoke the shell to produce a message like:
.DS
.DE
indicating that a file
`core' has been created containing information about the running program's
-state when it terminated due to the \s-2QUIT\s0 signal.
+state when it terminated due to the QUIT signal.
You can examine this file yourself, or forward information to the
maintainer of the program telling him/her where the
.I "core file"
is.
.PP
If you run background commands (as explained in section 2.6) then these
-commands will ignore \s-2INTERRUPT\s0 and \s-2QUIT\s0 signals at the
+commands will ignore INTERRUPT and QUIT signals at the
terminal. To stop them you must use the
.I kill
command. See section 2.6 for an example.
The remaining sections will go yet further into the internals of the
shell, but you will surely want to try using the
shell before you go any further.
-To try it you can log in to \s-2UNIX\s0 and type the following
+To try it you can log in to UNIX and type the following
command to the system:
.DS
chsh -s /bin/csh myname
-.\" $OpenBSD: csh.2,v 1.9 2004/04/21 08:11:15 jmc Exp $
+.\" $OpenBSD: csh.2,v 1.10 2010/07/22 08:30:29 jmc Exp $
.\" $NetBSD: csh.2,v 1.3 1995/03/21 09:03:35 cgd Exp $
.\"
.\" Copyright (c) 1980, 1993
.I \&.login
also in your home directory.
This file contains commands which you wish to do each time you log in
-to the \s-2UNIX\s0 system.
+to the UNIX system.
My
.I \&.login
file looks something like:
endif
.DE
.PP
-This file contains several commands to be executed by \s-2UNIX\s0
+This file contains several commands to be executed by UNIX
each time I log in.
The first is a
.I set
.PP
Next I set the shell variable `time' to `15' causing the shell to automatically
print out statistics lines for commands which execute for at least 15 seconds
-of \s-2CPU\s+2 time. The variable `history' is set to 10 indicating that
+of CPU time. The variable `history' is set to 10 indicating that
I want the shell to remember the last 10 commands I type in its
.I "history list" ,
(described later).
command) the shell
will print `logout' and execute commands from the file `.logout'
if it exists in my home directory.
-After that the shell will terminate and \s-2UNIX\s0 will log
+After that the shell will terminate and UNIX will log
me off the system.
If the system is not going down, I will receive a new login message.
In any case, after the `logout' message the shell is committed to terminating
by searching for a string which appeared in it, and there are other,
less useful, ways to select arguments to include in a new command.
A complete description of all these mechanisms
-is given in the C shell manual pages in the \s-2UNIX\s0 Programmer's Manual.
+is given in the C shell manual pages in the UNIX Programmer's Manual.
.NH 2
Aliases
.PP
`Done' message might have come right in the middle of the message to
Bill.
Background jobs are unaffected by any signals from the keyboard like
-the \s-2STOP\s0, \s-2INTERRUPT\s0, or \s-2QUIT\s0 signals mentioned earlier.
+the STOP, INTERRUPT, or QUIT signals mentioned earlier.
.PP
Jobs are recorded in a table inside the shell until they terminate.
In this table, the shell remembers the command names, arguments, and the
As mentioned in section 1.8, foreground jobs become
.I suspended
by typing ^Z,
-which sends a \s-2STOP\s0 signal to the currently running
+which sends a STOP signal to the currently running
foreground job. A background job can become suspended by using the
.I stop
command described below. When jobs are suspended they merely stop
.I bg
command runs a suspended job in the background. It is usually used
after stopping the currently running foreground job with the
-\s-2STOP\s0 signal. The combination of the \s-2STOP\s0 signal and the
+STOP signal. The combination of the STOP signal and the
.I bg
command changes a foreground job into a background job.
The
issued. In the above example the `ed' job was still in `/home/bill/project'
even though the shell had changed to `/home/bill'.
A similar warning is given when such a foreground job
-terminates or is suspended (using the \s-2STOP\s0 signal) since
+terminates or is suspended (using the STOP signal) since
the return to the shell again implies a change of working directory.
.DS
% fg
.DS
setenv TERM adm3a
.DE
-will set the value of the environment variable \s-2TERM\s0
+will set the value of the environment variable TERM
to
`adm3a'.
A user program
The
.I time
command can be used to cause a command to be timed no matter how much
-\s-2CPU\s0 time it takes.
+CPU time it takes.
Thus
.DS
% time cp /etc/rc /home/bill/rc
on the other hand used 0.1 seconds of user time and 0.1 seconds of system
time in less than a second of elapsed time.
The percentage `13%' indicates that over the period when it was active
-the command `wc' used an average of 13 percent of the available \s-2CPU\s0
+the command `wc' used an average of 13 percent of the available CPU
cycles of the machine.
.PP
The
built-in command which can be used to run the same command
sequence with a number of different arguments.
.PP
-If you intend to use \s-2UNIX\s0 a lot you should look through
+If you intend to use UNIX a lot you should look through
the rest of this document and the csh manual pages (section1) to become familiar
with the other facilities which are available to you.
.bp
-.\" $OpenBSD: csh.3,v 1.6 2004/08/03 09:39:42 jmc Exp $
+.\" $OpenBSD: csh.3,v 1.7 2010/07/22 08:30:29 jmc Exp $
.\" $NetBSD: csh.3,v 1.3 1995/03/21 09:03:38 cgd Exp $
.\"
.\" Copyright (c) 1980, 1993
Commands run from shell scripts receive by default the standard
input of the shell which is running the script.
This is different from previous shells running
-under \s-2UNIX\s0. It allows shell scripts to fully participate
+under UNIX. It allows shell scripts to fully participate
in pipelines, but mandates extra notation for commands which are to take
inline data.
.PP
-.\" $OpenBSD: csh.4,v 1.4 2004/04/21 08:11:15 jmc Exp $
+.\" $OpenBSD: csh.4,v 1.5 2010/07/22 08:30:29 jmc Exp $
.\" $NetBSD: csh.4,v 1.3 1995/03/21 09:03:39 cgd Exp $
.\"
.\" Copyright (c) 1980, 1993
.I foreach
control structure at the terminal to aid in performing a number
of similar commands.
-For instance, there were at one point three shells in use on the Cory \s-2UNIX\s0
+For instance, there were at one point three shells in use on the Cory UNIX
system at Cory Hall,
`/bin/sh',
`/bin/nsh',
These are detailed fully in its manual section.
.PP
The shell has a number of command line option flags mostly of use
-in writing \s-2UNIX\s0 programs,
+in writing UNIX programs,
and debugging shell scripts.
See the csh(1) manual section for a list of these options.
.bp
-.\" $OpenBSD: csh.a,v 1.4 2003/06/02 23:32:07 millert Exp $
+.\" $OpenBSD: csh.a,v 1.5 2010/07/22 08:30:29 jmc Exp $
.\" $NetBSD: csh.a,v 1.3 1995/03/21 09:03:41 cgd Exp $
.\"
.\" Copyright (c) 1980, 1993
.LP
The following table lists the special characters of
.I csh
-and the \s-2UNIX\s0 system, giving for each the section(s) in which it
+and the UNIX system, giving for each the section(s) in which it
is discussed.
A number of these characters also have special meaning in expressions.
See the
-.\" $OpenBSD: csh.g,v 1.6 2004/04/21 08:11:15 jmc Exp $
+.\" $OpenBSD: csh.g,v 1.7 2010/07/22 08:30:29 jmc Exp $
.\" $NetBSD: csh.g,v 1.3 1995/03/21 09:03:42 cgd Exp $
.\"
.\" Copyright (c) 1980, 1993
pr(1)
indicate that the command
.I pr
-is in the \s-2UNIX\s0 User Reference manual in section 1.
+is in the UNIX User Reference manual in section 1.
You can look at an online copy of its manual page by doing
.DS
man 1 pr
.IP alias
An
.I alias
-specifies a shorter or different name for a \s-2UNIX\s0
+specifies a shorter or different name for a UNIX
command, or a transformation on a command to be performed in
the shell.
The shell has a command
.I aliases
(2.4).
.IP argument
-Commands in \s-2UNIX\s0 receive a list of
+Commands in UNIX receive a list of
.I argument
words.
Thus the command
A command executed directly by the shell is called a
.I builtin
command.
-Most commands in \s-2UNIX\s0 are not built into the shell,
+Most commands in UNIX are not built into the shell,
but rather exist as files in
.I bin
directories.
.IP chsh
The
.I chsh
-command is used to change the shell which you use on \s-2UNIX\s0.
+command is used to change the shell which you use on UNIX.
By default, you use a different version of the shell
which resides in `/bin/sh'.
You can change your shell to `/bin/csh' by doing
chsh -s /bin/csh bill
.DE
It is only necessary to do this once.
-The next time you log in to \s-2UNIX\s0 after doing this command,
+The next time you log in to UNIX after doing this command,
you will be using
.I csh
rather than the shell in `/bin/sh' (1.9).
(a builtin
.I command )
or by a program residing in a file in
-a directory within the \s-2UNIX\s0 system, is called a
+a directory within the UNIX system, is called a
.I command
(1.1).
.IP "command name"
.I "command name" ,
which is the first word of the command,
followed by arguments.
-The convention on \s-2UNIX\s0 is that the first word of a
+The convention on UNIX is that the first word of a
command names the function to be performed (1.1).
.IP "command substitution"
.br
.IP control-
Certain special characters, called
.I control
-characters, are produced by holding down the \s-2CONTROL\s0 key
+characters, are produced by holding down the CONTROL key
on your terminal and simultaneously pressing another character, much like
-the \s-2SHIFT\s0 key is used to produce upper case characters. Thus
+the SHIFT key is used to produce upper case characters. Thus
.I control- c
-is produced by holding down the \s-2CONTROL\s0 key while pressing the
-`c' key. Usually \s-2UNIX\s0 prints an caret (^) followed by the
+is produced by holding down the CONTROL key while pressing the
+`c' key. Usually UNIX prints an caret (^) followed by the
corresponding letter when you type a
.I control
character (e.g. `^C' for
.I cp
(copy) program is used to copy the contents of one file into another
file.
-It is one of the most commonly used \s-2UNIX\s0 commands (1.6).
+It is one of the most commonly used UNIX commands (1.6).
.IP csh
The name of the shell
program that this document describes.
to label the code to be executed if none of the
.I case
labels matches the value switched on (3.7).
-.IP \s-2DELETE\s0
+.IP DELETE
The
-\s-2DELETE\s0
+DELETE
or
-\s-2RUBOUT\s0
+RUBOUT
key on the terminal normally causes an interrupt to be sent to the current job.
Most users map the interrupt character to ^C.
.IP detached
are executed if the condition between parentheses after the
.I if
is true (3.6).
-.IP \s-2EOF\s0
+.IP EOF
An
.I "end\f1-\fPof\f1-\fPfile"
is generated by the terminal by a control-d,
There is also a non-printing character called
.I escape ,
usually labelled
-\s-2ESC\s0
+ESC
or
-\s-2ALTMODE\s0
+ALTMODE
on terminal keyboards.
-Some older \s-2UNIX\s0 systems use this character to indicate that
+Some older UNIX systems use this character to indicate that
output is to be
.I suspended .
Most systems use control-s to stop the output and control-q to start it.
.I foreground
(1.8, 2.6).
.IP filename
-Each file in \s-2UNIX\s0 has a name consisting of up to 14 characters
+Each file in UNIX has a name consisting of up to 14 characters
and not including the character `/' which is used in
.I pathname
building. Most
mechanisms use the metacharacter `~' and allow
files in other users' directories to be named easily (1.6, 4.2).
.IP flag
-Many \s-2UNIX\s0 commands accept arguments which are not the names
+Many UNIX commands accept arguments which are not the names
of files or other users but are used to modify the action of the commands.
These are referred to as
.I flag
characters, logging yourself off
(2.2).
.IP input
-Many commands on \s-2UNIX\s0 take information from the terminal or from
+Many commands on UNIX take information from the terminal or from
files which they then act on.
This information is called
.I input .
An
.I interrupt
is a signal to a program that is generated by typing ^C. (On older versions
-of UNIX the \s-2RUBOUT\s0 or \s-2DELETE\s0 key were used for this purpose.)
+of UNIX the RUBOUT or DELETE key were used for this purpose.)
It causes most programs to stop execution.
Certain programs, such as the shell and the editors,
handle an
.I \&.login
in your
.I home
-directory is read by the shell each time you log in to \s-2UNIX\s0
+directory is read by the shell each time you log in to UNIX
and the commands there are executed.
There are a number of commands which are usefully placed here,
especially
.I \&.login
file then this will not work and you must use
.I logout
-to log off the \s-2UNIX\s0 system (2.8).
+to log off the UNIX system (2.8).
.IP \&.logout
-When you log off \s-2UNIX\s0 the shell will execute commands from
+When you log off UNIX the shell will execute commands from
the file
.I \&.logout
in your
is the line printer daemon.
The standard input of
.I lpr
-spooled and printed on the \s-2UNIX\s0 line printer.
+spooled and printed on the UNIX line printer.
You can also give
.I lpr
a list of filenames as arguments to be printed.
.IP ls
The
.I ls
-(list files) command is one of the most commonly used \s-2UNIX\s0
+(list files) command is one of the most commonly used UNIX
commands.
With no argument filenames it prints the names of the files in the
current directory.
.IP mail
The
.I mail
-program is used to send and receive messages from other \s-2UNIX\s0
+program is used to send and receive messages from other UNIX
users (1.1, 2.1), whether they are logged on or not.
.IP make
The
The
.I manual
often referred to is the
-`\s-2UNIX\s0 manual'.
-It contains 9 numbered sections with a description of each \s-2UNIX\s0
+`UNIX manual'.
+It contains 9 numbered sections with a description of each UNIX
program (section 1), system call (section 2), subroutine (section 3),
device (section 4), special data structure (section 5), game (section 6),
miscellaneous item (section 7), system administration program (section 8),
.IP metacharacter
.br
Many characters which are neither letters nor digits have special meaning
-either to the shell or to \s-2UNIX\s0.
+either to the shell or to UNIX.
These characters are called
.I metacharacters .
If it is necessary to place these characters in arguments to commands
.I interrupt
signal is received (3.9).
.IP output
-Many commands in \s-2UNIX\s0 result in some lines of text which are
+Many commands in UNIX result in some lines of text which are
called their
.I output .
This
An instance of a running program is called a
.I process
(2.6).
-\s-2UNIX\s0 assigns each
+UNIX assigns each
.I process
a unique number when it is
started \- called the
an indication of the terminal name it is attached to,
an indication of the state of the process (whether it is running,
stopped, awaiting some event (sleeping), and whether it is swapped out),
-and the amount of \s-2CPU\s0 time it has used so far.
+and the amount of CPU time it has used so far.
The command is identified by printing some of the words used
when it was invoked (2.6).
.\" Shells, such as the
See
.I filename
for a further explanation (1.6).
-.IP \s-2RUBOUT\s0
-The \s-2RUBOUT\s0 or \s-2DELETE\s0
+.IP RUBOUT
+The RUBOUT or DELETE
key is often used to erase the previously typed character; some users
-prefer the \s-2BACKSPACE\s0 for this purpose. On older versions of \s-2UNIX\s0
-this key served as the \s-2INTR\s0 character.
+prefer the BACKSPACE for this purpose. On older versions of UNIX
+this key served as the INTR character.
.IP "scratch file"
Files whose names begin with a `#' are referred to as
.I "scratch files" ,
.IP signal
A
.I signal
-in \s-2UNIX\s0 is a short message that is sent to a running program
+in UNIX is a short message that is sent to a running program
which causes something to happen to that process.
.I Signals
are sent either by typing special
.IP stty
The
.I stty
-program changes certain parameters inside \s-2UNIX\s0 which determine
+program changes certain parameters inside UNIX which determine
how your terminal is handled. See stty(1) for a complete description (2.6).
.IP substitution
The shell implements a number of
.IP suspended
A job becomes
.I suspended
-after a \s-2STOP\s0 signal is sent to it, either by typing a
+after a STOP signal is sent to it, either by typing a
.I control -z
at the terminal (for
.I foreground
.IP time
The
.I time
-command can be used to measure the amount of \s-2CPU\s0
+command can be used to measure the amount of CPU
and real time consumed by a specified command as well
as the amount of disk I/O, memory utilized, and number
of page faults and swaps taken by the command (2.1, 2.8).
The word
.I tty
is a historical abbreviation for `teletype' which is frequently used
-in \s-2UNIX\s0 to indicate the
+in UNIX to indicate the
.I port
to which a given terminal is connected. The
.I tty
The
.I unalias
command removes aliases (2.8).
-.IP \s-2UNIX\s0
-\s-2UNIX\s0 is an operating system on which
+.IP UNIX
+UNIX is an operating system on which
.I csh
runs.
-\s-2UNIX\s0 provides facilities which allow
+UNIX provides facilities which allow
.I csh
to invoke other programs such as editors and text formatters which
you may wish to use.
The
.I write
command is an obsolete way of communicating with other users who are logged in to
-\s-2UNIX\s0 (you have to take turns typing). If you are both using display
+UNIX (you have to take turns typing). If you are both using display
terminals, use talk(1), which is much more pleasant.
-.\" $OpenBSD: cu.1,v 1.12 2010/06/29 23:32:52 nicm Exp $
+.\" $OpenBSD: cu.1,v 1.13 2010/07/22 08:32:58 jmc Exp $
.\"
.\" Copyright (c) 1980, 1990, 1993
.\" The Regents of the University of California. All rights reserved.
.\"
.\" @(#)tip.1 8.4 (Berkeley) 4/18/94
.\"
-.Dd $Mdocdate: June 29 2010 $
+.Dd $Mdocdate: July 22 2010 $
.Dt CU 1
.Os
.Sh NAME
system is processed by the shell.
.It Ic ~C
Fork a child process on the local system to perform special protocols
-such as \s-1XMODEM\s+1.
+such as XMODEM.
The child program will be run with the following arrangement of
file descriptors:
.Bd -literal -offset indent
-.\" $OpenBSD: tip.1,v 1.41 2010/06/29 16:41:56 nicm Exp $
+.\" $OpenBSD: tip.1,v 1.42 2010/07/22 08:32:58 jmc Exp $
.\" $NetBSD: tip.1,v 1.7 1994/12/08 09:31:05 jtc Exp $
.\"
.\" Copyright (c) 1980, 1990, 1993
.\"
.\" @(#)tip.1 8.4 (Berkeley) 4/18/94
.\"
-.Dd $Mdocdate: June 29 2010 $
+.Dd $Mdocdate: July 22 2010 $
.Dt TIP 1
.Os
.Sh NAME
system is processed by the shell.
.It Ic ~C
Fork a child process on the local system to perform special protocols
-such as \s-1XMODEM\s+1.
+such as XMODEM.
The child program will be run with the following arrangement of
file descriptors:
.Bd -literal -offset indent
-.\" $OpenBSD: map3270.5,v 1.9 2003/06/03 02:56:19 millert Exp $
+.\" $OpenBSD: map3270.5,v 1.10 2010/07/22 08:32:58 jmc Exp $
.\" Copyright (c) 1986 The Regents of the University of California.
.\" All rights reserved.
.\"
.SH SYNOPSIS
.B map3270
.SH DESCRIPTION
-When emulating IBM-style 3270 terminals under \s-1UNIX\s0 (see \fItn3270\fR(1)),
+When emulating IBM-style 3270 terminals under UNIX (see \fItn3270\fR(1)),
a mapping must be performed between sequences of keys hit on
a user's (ASCII) keyboard, and the keys that are
available on a 3270. For example, a 3270 has a key labeled
projects / openbsd / commitdiff