text.tex

早期freebsd实现

Hence,
\example folder\ +inbox\endexample
makes \eg{+inbox} the current folder.

After a using \pgm{rmm} and \pgm{refile} on a folder a number of times,
there tend to be gaps in the numbering sequence.
To compress the numbers for the all messages in a folder,
use
\example folder\ -pack\endexample

\section{The Profile}
You can customize the \MH/ environment by editing your \profile/ file.
Although there are lots of options,
here are the most useful:
\smallskip
{\advance\leftskip by\parindent
\item{\underbar{Editor}:} lists the default editor that \pgm{comp} and
\pgm{repl} should use.
The default is
\example editor:\ prompter\endexample
but another editor might be preferred.

\item{\underbar{{\it editor}-next}:} lists the editor that should be used
after the last edit with {\it editor}.
Hence, if you have a profile entry
\example prompter-next:\ vi\endexample
after editing a draft with \pgm{prompter},
and being at \whatnow/ level,
you could say \eg{edit} (instead of \eg{edit vi})
to continue to edit the draft with \pgm{vi}.

\item{\underbar{Msg-Protect}:}
Whenever \MH/ creates a message (for example, with \pgm{inc\/}),
this is the octal protection mode that the message is created with.
The default is
\example Msg-Protect:\ 644\endexample
This protection mode permits all other users on the system to read
your messages.
To maintain privacy, the mode 600 should be used.
Note that changing the mode in the profile does not change the modes
of messages that have been created already.
Use the \unix/ command \pgm{chmod} to change the modes of your
existing messages.

\item{\underbar{Folder-Protect}:}
Whenever \MH/ creates a folder (for example, with \pgm{refile\/}),
this is the octal mode that the folder is created with.
The default is
\example Folder-Protect:\ 711\endexample
This mode permits other users on the system to make access to
specific messages in your folders.
To maintain stricter privacy, the mode 700 should be used.

\item{\underbar{{\it program\/}}:}
Each \MH/ program that reads user's \profile/ file
looks for an entry beginning with its own
name to determine its initial defaults.
For example,
if you want the default editor for \pgm{repl} to be \pgm{emacs},
the line
\example repl:\ -editor\ emacs\endexample
is sufficient.
Command line arguments tend to override profile settings.
Given the profile setting for \pgm{repl} above,
if you invoked \pgm{repl} with
\example repl\ -editor\ vi\endexample
\pgm{repl} would use the \pgm{vi} editor instead
of \pgm{emacs}.

\item{\underbar{signature}:}
When \MH/ posts mail for you,
it looks for this profile entry for your ``real world'' name.
For example,
\example signature:\ Marshall\ Rose\endexample
The contents of the \eg{signature:} entry in the profile should be a simple
phrase, with no embedded periods (e.g. ``Marshall T.~Rose'').
\medskip}
\noindent
Note that your profile resembles the header portion of a message.
Be sure that it is properly formatted by placing a colon after each entry
name,
and keep each entry on a single line.

\section{Conventions}
Now let's summarize the conventions that \MH/ programs use:
\smallskip
{\advance\leftskip by\parindent
\item{1.} Any \MH/ command that deals with messages can be given a
\arg{+folder} argument to say which folder to use.
However, only one \arg{+folder} argument may be given per command
in most cases.

\item{2.} If an \MH/ command accepts a \arg{msgs} argument,
then any number of messages can be given to the command.
The \MH/ command will expand all the ranges and process each message,
starting with the lowest numbered one and working its way to the message with
the highest number.

\item{3.} If an \MH/ command accepts a \arg{msg} argument,
then at most one message can be given.

\item{4.} Switches (options) to \MH/ commands start with a dash.
Unlike the standard \unix/ convention,
each switch consists of more than one character,
for example \switch{header}.
To minimize typing,
only a unique abbreviation of the switch need be typed;
thus for \switch{header}, \switch{hea} is probably sufficient,
depending on the other switches accepted by the command.

\item{5.} All \MH/ commands have a \switch{help} switch,
which {\it must} be spelled out fully.
When an \MH/ command encounters the \switch{help} switch,
it prints out the syntax of the command,
the switches that it accepts,
and version information.
In the list of switches,
parentheses indicate required characters.
For example,
all \switch{help} switches will appear as \switch{(help)},
indicating that no abbreviation is accepted.

\item{6.} Many \MH/ switches have both on and off forms,
such as \switch{format} and \switch{noformat}.
In these cases,
the last occurrence of the switch on the command line determines the setting
of the option.

\item{7.} All \MH/ commands that read your \MH/ profile operate the
same way:
\underbar{first},
the profile is consulted for an entry matching the name with which
the command was invoked;
\underbar{second},
if such an entry was found,
then the command immediately uses the arguments listed;
\underbar{third},
any arguments on the command line are then interpreted.
Since most switches have both on and off forms,
it's easy to customize the default options for each \MH/ command in the
\profile/,
and to override those defaults on the command line.
\smallskip}

\section{Online Documentation}
Each \MH/ program has its own \unix/ manual entry.
For example, to get information about \pgm{comp},
type
\example man\ comp\endexample
The manual entry for \man mh(1) lists all \MH/ commands,
while the manual entry for \man mh-chart(1) lists the syntax and switches for
all \MH/ commands.

In addition,
here are a few other manual entries might be found useful:
\smallskip
{\advance\leftskip by\parindent
\item{\man mh-alias(5)} to find out how aliases in \MH/ work;
\item{\man mh-mail(5)} to find out how \MH/ stores and interprets messages
(this manual entry explains all of the standard header components);
\item{\man mh-profile(5)} to find out about the \MH/ user-environment.
\smallskip}

The manual pages for \MH/ are in the standard \unix/ format,
but contain additional sections unique to \MH/.
Here's a summary of the sections one might find in an \MH/ manual entry:
\smallskip
{\advance\leftskip by\parindent
\item{\sc Name} command name and one-line description.

\item{\sc Synopsis} syntax of the command.\hbreak
All commands accept a \switch{help} switch.

\item{\sc Description} semantics of the command.

\item{\sc Files} files used by the command\hbreak
Almost always this includes \file{.mh\_profile}.

\item{\sc Profile} entries in the \profile/ used by the command;
\vskip -\parskip
\item{\sc Components} these do not include the profile entry for the
command itself.

\item{\sc See Also} other \unix/ manual entries (usually \MH/ programs) that
are related to this command.

\item{\sc Defaults} default arguments for the command\hbreak
If the command takes a \arg{+folder} argument,
this defaults to the current folder.
If the command takes a \arg{msg} argument,
this defaults to the current message.
If the command takes a \arg{msgs} argument,
this defaults to the current message or all messages,
depending on which one makes more sense.

\item{\sc Context} changes to your \MH/ context made by the command.

\item{\sc Hints} Helpful hints discussing the easy way to do things.

\item{\sc History} A historical perspective on why \MH/ works the way it does.

\item{\sc Bugs} Too embarrassing to mention.\hbreak
Just kidding.
\medskip}
\noindent
Obviously, not all \MH/ manual entries may have all of these sections.

\section{Reporting Problems}
If problems are encountered with an \MH/ program,
the problems should be reported to the local maintainers of \MH/.
When doing this,
the name of the program should be reported,
along with the version information for the program.
To find out what version of an \MH/ program is being run,
invoke the program with the \switch{help} switch.
In addition to listing the syntax of the command,
the program will list information pertaining to its version.
This information includes the version of \MH/,
the host it was generated on,
the date the program was loaded,
and the configuration options in effect when \MH/ was generated.
For example,
\example
    version: MH 6.1 \#1[UCI] (gremlin) of Wed Nov  6 01:13:53 PST 1985\\
    options: [BSD42] [MHE] [NETWORK] [SENDMTS] [MMDFII] [SMTP] [POP]\endexample
The \eg{6.1~\#1[UCI]} indicates that the program is from the UCI \mh6
version of \MH/.
The program was generated on the host \eg{gremlin} on
\eg{Wed Nov  6 01:13:53 PST 1985}.
It's usually a good idea to send the output of the \switch{help} switch along
with your report.

If there is no local \MH/ maintainer,
try the address {\tx Bug-MH}.
If that fails, use the Internet mailbox {\tx [e-mail]}.

\section{More on MH}
There are myriad aspects of \MH/ that this tutorial hasn't touched upon.
Here are a few to whet your appetite:
\smallskip
{\advance\leftskip by\parindent
\item{1.} user-defined sequences\hbreak
Define {\it meaningful} message names and shorten type-in considerably
(see \man pick(1) for details).

\item{2.} draft folders\hbreak
Maintain a folder of drafts so that more than one draft can be edited at a
time,
and allow a draft to be edited over several \unix/ sessions independently of
other drafts
(see the {\bf Advanced Features} section of the \MH/ user's manual for
details).

\item{3.} draft pushing\hbreak
Post a draft in the background
and immediately free your terminal for other activities
(see the {\bf Advanced Features} section of the \MH/ user's manual for
details).

\item{4.} aliases\hbreak
Maintain one or more alias files containing the addresses of the people
frequently (or infrequently) sent to.
This lets you shorten type-in of addressees
and saves you from looking up
their addresses all the time.
(see \man mh-alias(5) for details).
\smallskip}