comp − compose a message comp [+folder] [msg] [−draftfolder +folder] [−draftmessage msg] [−nodraftfolder] [−editor editor] [−noedit] [−file file] [−form formfile] [−use] [−nouse] [−whatnowproc program] [−nowhatnowproc] [−help]
DESCRIPTION
Comp is used to create a new message to be mailed. It copies a message form to the draft being composed and then invokes an editor on the draft (unless ‘−noedit’ is given, in which case the initial edit is suppressed).
The default message form contains the following elements:
If the file named “components” exists in the user’s MH directory, it will be used instead of this form. The file specified by ‘−form formfile’ will be used if given. You may also start comp using the contents of an existing message as the form. If you supply either a ‘+folder’ or ‘msg’ argument, that message will be used as the form. You may not supply both a ‘−form formfile’ and a ‘+folder’ or ‘msg’ argument. The line of dashes or a blank line must be left between the header and the body of the message for the message to be identified properly when it is sent (see send (1)). The switch ‘−use’ directs comp to continue editing an already started message. That is, if a comp (or dist, repl, or forw ) is terminated without sending the draft, the draft can be edited again via “comp −use”.
If the draft already exists, comp will ask you as to the disposition of the draft. A reply of quit will abort comp, leaving the draft intact; replace will replace the existing draft with the appropriate form; list will display the draft; use will use the draft for further composition; and refile +folder will file the draft in the given folder, and give you a new draft with the appropriate form. (The ‘+folder’ argument to refile is required.)
The ‘−draftfolder +folder’ and ‘−draftmessage msg’ switches invoke the MH draft folder facility. This is an advanced (and highly useful) feature. Consult the Advanced Features section of the MH manual for more information.
The ‘−file file’ switch says to use the named file as the message draft.
Comp normally converts a message to JIS code, however, if ‘−nocnv’ is specified, comp does not.
Upon exiting from the editor, comp will invoke the whatnow program. See whatnow (1) for a discussion of available options. The invocation of this program can be inhibited by using the ‘−nowhatnowproc’ switch. (In truth of fact, it is the whatnow program which starts the initial edit. Hence, ‘−nowhatnowproc’ will prevent any edit from occurring.) ^/usr/new/lib/mh/components~^The message skeleton ^or <mh−dir>/components~^Rather than the standard skeleton ^$HOME/.mh_profile~^The user profile ^<mh−dir>/draft~^The draft file ^Path:~^To determine the user’s MH directory ^Draft−Folder:~^To find the default draft−folder ^Editor:~^To override the default editor ^Msg−Protect:~^To set mode when creating a new message (draft) ^fileproc:~^Program to refile the message ^whatnowproc:~^Program to ask the “What now?” questions dist(1), forw(1), repl(1), send(1), whatnow(1) ‘+folder’ defaults to the current folder ‘msg’ defaults to the current message ‘−nodraftfolder’ ‘−nouse’ None If whatnowproc is whatnow, then comp uses a built−in whatnow, it does not actually run the whatnow program. Hence, if you define your own whatnowproc, don’t call it whatnow since comp won’t run it.
NEWS-OSRelease 3.3