1COMP(1)                            [nmh-1.3]                           COMP(1)
2
3
4

NAME

6       comp - compose a message
7

SYNOPSIS

9       comp [+folder] [msgs] [-form formfile] [-use | -nouse] [-file file]
10            [-draftfolder +folder] [-draftmessage msg] [-nodraftfolder] [-edi‐
11            tor editor] [-noedit] [-whatnowproc program] [-nowhatnowproc]
12            [-version] [-help]
13

DESCRIPTION

15       Comp is used to create a new message to be mailed.  It copies a message
16       form  to  the  draft  being  composed and then invokes an editor on the
17       draft (unless -noedit is given, in which case the initial edit is  sup‐
18       pressed).
19
20       The default message form contains the following elements:
21
22            To:
23            cc:
24            Fcc: +outbox
25            Subject:
26            --------
27
28       If  a  file  named  “components” exists in the user's nmh directory, it
29       will be used instead of this form.  You may specify an alternate  forms
30       file with the switch -form formfile.
31
32       You  may  also  start comp using the contents of an existing message as
33       the form.  If you supply either a +folder or msg argument, that message
34       will  be  used  as  the  message form.  You may not supply both a -form
35       formfile and a +folder or msg argument.  The line of dashes or a  blank
36       line  must  be  left between the header and the body of the message for
37       the message to be identified properly when it is sent (see send(1)).
38
39       The switch -use directs comp to continue  editing  an  already  started
40       message.   That  is,  if  a comp (or dist, repl, or forw) is terminated
41       without sending the draft, the draft can  be  edited  again  via  “comp
42       -use”.
43
44       The -file file switch says to use the named file as the message draft.
45
46       If the draft already exists, comp will ask you as to the disposition of
47       the draft.  A reply of quit will abort comp, leaving the draft  intact;
48       replace will replace the existing draft with the appropriate form; list
49       will display the draft; use will use the draft for further composition;
50       and  refile  +folder  will file the draft in the given folder, and give
51       you a new draft with the appropriate form.  (The  +folder  argument  to
52       refile is required.)
53
54       The  -draftfolder +folder and -draftmessage msg switches invoke the nmh
55       draft folder facility.  This is an advanced (and  highly  useful)  fea‐
56       ture.  Consult the mh-draft(5) man page for more information.
57
58       The  -editor  editor switch indicates the editor to use for the initial
59       edit.  Upon exiting from the editor, comp will invoke the whatnow  pro‐
60       gram.  See whatnow(1) for a discussion of available options.  The invo‐
61       cation of this program can be inhibited  by  using  the  -nowhatnowproc
62       switch.   (In truth of fact, it is the whatnow program which starts the
63       initial edit.  Hence, -nowhatnowproc will prevent any edit from  occur‐
64       ring.)
65
66

FILES

68       /etc/nmh/components        The standard message skeleton
69       or <mh-dir>/components     Rather than the standard skeleton
70       $HOME/.mh_profile          The user profile
71       <mh-dir>/draft             The draft file
72
73

PROFILE COMPONENTS

75       Path:                To determine the user's nmh directory
76       Draft-Folder:        To find the default draft-folder
77       Editor:              To override the default editor
78       Msg-Protect:         To set mode when creating a new message (draft)
79       fileproc:            Program to refile the message
80       whatnowproc:         Program to ask the “What now?” questions
81
82

SEE ALSO

84       dist(1), forw(1), repl(1), send(1), whatnow(1), mh-profile(5)
85
86

DEFAULTS

88       `+folder' defaults to the current folder
89       `msg' defaults to the current message
90       `-nodraftfolder'
91       `-nouse'
92
93

CONTEXT

95       None
96
97

BUGS

99       If  whatnowproc  is whatnow, then comp uses a built-in whatnow, it does
100       not actually run the whatnow program.  Hence, if you  define  your  own
101       whatnowproc, don't call it whatnow since comp won't run it.
102
103
104
105MH.6.8                            1 June 2008                          COMP(1)
Impressum