os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

+ Add tags to filename/command instances.

Browse source 
+ Add a comma to separate parts of existing sentences more clearly.
+ Change "Also you might want" to "You might also want".
+ Remove a duplicate <command>edit</command>.
+ Reword and split sentences, minor other grammar fixes.
This commit is contained in:
Giorgos Keramidas 2002-05-13 10:40:26 +00:00
parent 53b6c5c504
commit b1733ff0d6
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=13063
1 changed files with 15 additions and 14 deletions

29
en_US.ISO8859-1/articles/mh/article.sgml
View file

@ -46,7 +46,7 @@
email MH has done an excellent job keeping the configuration of
each of these tools consistent and uniform. In fact, if you are
not quite sure how something is supposed to work or what the
arguments for some command are supposed to be then you can
arguments for some command are supposed to be, then you can
generally guess and be right. Each MH command is consistent
about how it handles reading the configuration files and how it
takes arguments on the command line. One useful thing to
@ -73,7 +73,7 @@
<para>This primer is not a full comprehensive explanation of how
MH works. This is just intended to get you started on the road
to happier, faster mail reading. You should read the man pages
for the various commands. Also you might want to read the <ulink
for the various commands. You might also want to read the <ulink
URL="news:comp.mail.mh">comp.mail.mh</ulink> newsgroup. Also
you can read the <ulink
URL="http://www.cis.ohio-state.edu/hypertext/faq/usenet/mh-faq/part1/faq.html">FAQ
@ -88,7 +88,7 @@
<command>show</command>, <command>scan</command>, <command>next</command>,
<command>prev</command>, <command>rmm</command>, <command>rmf</command>, and
<command>msgchk</command>. One of the best things about MH is the
consistent interface between programs. A few things to keep in
consistent interface between programs. One thing to keep in
mind when using these commands is how to specify message lists.
In the case of <command>inc</command> this does not really make any
sense but with commands like <command>show</command> it is useful to
@ -112,7 +112,7 @@
<keycap>return</keycap> you will be well on your way to getting
started with MH. The first time you run <command>inc</command> it
will setup your account to use all the MH defaults and ask you
about creating a Mail directory. If you have mail waiting to
about creating a <filename>Mail</filename> directory under your HOME directory. If you have mail waiting to
be downloaded you will see something that looks like:</para>
<informalexample>
@ -144,7 +144,7 @@
plain POP3 for downloading your email. MH has support for a
few different dialects of POP. More than likely you will never
ever need to use them though. While you can do more complex
things with inc such as audit files and scan format files this
things with <command>inc</command> such as audit files and scan format files this
will get you going.</para>
<para>The <command>msgchk</command> command is used to get information
@ -340,7 +340,7 @@ which I am probably the guilty party).</screen>
<para>Whenever you create a new folder a new directory is going to
be created underneath your MH <filename>Mail</filename> directory, and
messages in that folder are going to be stored in that
directory. When new email comes in that new email is thrown
directory. When a new email message comes, it is thrown
into your <filename>inbox</filename> directory with a file name that is
equivalent to the message number. So even if you did not have
any of the MH tools to read your email you could still use
@ -449,7 +449,7 @@ which I am probably the guilty party).</screen>
<term><option>-date</option></term>
<listitem>
<para>find emails with a matching dat</para>
<para>find emails with a matching date</para>
</listitem>
</varlistentry>
@ -513,7 +513,7 @@ which I am probably the guilty party).</screen>
not cc'd on freebsd-questions) and the subject is
pci</quote>. It should look through your folder and find
all messages sent to the freebsd-hackers list that are not cc'd
to the freebsd-questions list that contain something on pci in
to the freebsd-questions list and contain <quote>pci</quote> in
the subject line. Ordinarily you might have to worry about
something called operator precedence. Remember in math how you
evaluate from left to right and you do multiplication and
@ -599,10 +599,10 @@ which I am probably the guilty party).</screen>
Subject: headers already in it. You are then sent into your
editor where you fill in the header information and then type
the body of your message below the dashed lines in the message.
Then to the <command>whatnow</command> program. When you are at the
When you leave the editor, the <command>whatnow</command> program is run. When you are at the
<prompt>What now?</prompt> prompt you can tell it to
<command>send</command>, <command>list</command>, <command>edit</command>,
<command>edit</command>, <command>push</command>, and <command>quit</command>. Most
<command>push</command>, and <command>quit</command>. Most
of these commands are self-explanatory. So the message sending
process involves copying a component file, editing your email,
and then telling the <command>whatnow</command> program what to do with
@ -654,8 +654,9 @@ Subject:<userinput>And on the 8th day God created the FreeBSD core team</userinp
will see the <prompt>What now?</prompt> prompt and you can type in
<userinput>send</userinput> or <userinput>s</userinput> and hit
<keycap>return</keycap>. Then the FreeBSD core team will receive
their just rewards. As I mentioned earlier you can also use
other commands, for example <command>quit</command> if you do not want
their just rewards. As I mentioned earlier, you can also use
other commands at the <prompt>What now?</prompt> prompt.
For example you can use <command>quit</command>, if you do not want
to send the message.</para>
<para>The <command>forw</command> command is stunningly similar. The
@ -669,8 +670,8 @@ Subject:<userinput>And on the 8th day God created the FreeBSD core team</userinp
exactly the same as <command>comp</command>. You go through the exact
same message sending process.</para>
<para>The <command>repl</command> command will reply to whatever your
current message is, unless you give it a different message to
<para>The <command>repl</command> command will reply to the
current message, unless you give it a different message to
reply to. <command>repl</command> will do its best to go ahead and
fill in some of the email headers already. So you will notice
that the <literal>To:</literal> header already has the address of the