Updated the man pages to the recent changes.

[mmh] / man / mhbuild.man1

diff --git a/man/mhbuild.man1 b/man/mhbuild.man1
index 280782e..3d3260f 100644 (file)
--- a/man/mhbuild.man1
+++ b/man/mhbuild.man1
@@ -482,62 +482,18 @@ through mail gateways which involve the EBCDIC character encoding.
 .SS "Invoking mhbuild"
 Typically,
 .B mhbuild
- is invoked by the
-.B whatnow
-program.  This
-command will expect the body of the draft to be formatted as an
-.B mhbuild
-composition file.  Once you have composed this input file
-using a command such as
-.BR comp ,
-.BR repl ,
-or
-.BR forw ,
-you invoke
-.B mhbuild
-at the \*(lqWhat now\*(rq prompt with
-.PP
-.RS 5
-What now? mime
-.RE
-.PP
-prior to sending the draft.  This will cause
-.B whatnow
-to execute
-.B mhbuild
-to translate the composition file into MIME format.
-.PP
-It is also possible to have the
-.B whatnow
-program invoke
-.B mhbuild
-automatically when a message is sent.  To do this, you must add the line
-.PP
-.RS 5
-automimeproc: 1
-.RE
-.PP
-to your
-.I .mmh/profile
-file.
-.PP
-Finally, you should consider adding this line to your profile:
-.PP
-.RS 5
-lproc: show
-.RE
-.PP
-This way, if you decide to
-.B list
-after invoking
-.BR mime ,
-the command
-.PP
-.RS 5
-What now? list
-.RE
-.PP
-will work as you expect.
+is invoked by the
+.B send
+program.
+It expects an
+.B mhbuild
+composition file, which
+.B send
+will create, from the draft file, if MIME features are requested.
+This is the case with attachment headers.
+.PP
+In contrast to previous versions, the user does not need to care
+for any special actions anymore.
 
 .SS "User Environment"
 Because the environment in which