head 1.4; access; symbols; locks; strict; comment @# @; 1.4 date 2006.05.29.14.31.25; author jpeek; state Exp; branches; next 1.3; 1.3 date 2006.05.28.04.27.15; author jpeek; state Exp; branches; next 1.2; 1.2 date 2006.05.26.23.59.01; author jpeek; state Exp; branches; next 1.1; 1.1 date 2006.05.26.22.12.07; author jpeek; state Exp; branches; next ; desc @mh-e_41.html page from mh-e section of "MH & nmh: Email for Users & Programmers" @ 1.4 log @Removed 'html/' from end of http://mh-e.sourceforge.net/manual/html/ URLs @ text @
This section of MH & nmh: Email for Users & Programmers is now the MH-E Manual. It's moved to http://mh-e.sourceforge.net/manual/.
If you aren't taken to the new site in 15 seconds, please click on the link above.
You may also want to visit:
mh-e does offer a couple of commands that are not a part of MH. The
first one, C-o (
mh-write-msg-to-file), writes a message to
a file (think of the o as in "output"). You are prompted for the
filename. If the file already exists, the message is appended to it.
You can also write the message to the file without the header by
specifying a prefix argument (such as C-u C-o /tmp/foobar RET).
Subsequent writes to the same file can be made with the !
You can also pipe the message through a Unix shell command with the
mh-pipe-msg) command. You are prompted for the
Unix command through which you wish to run your message. If you
give an argument to this command, the message header is included in the
text passed to the command (the contrived example C-u | lpr
would be done with the l command instead).
If the message is a shell archive
shar or has been run through
uuencode use M-n (
mh-store-msg) to extract the body
of the message. The default directory for extraction is the current
directory, and you have a chance to specify a different extraction
directory. The next time you use this command, the default directory is
the last directory you used.
Go to the first, previous, next, last section, table of contents.