1WHATNOW(1)                   [nmh-1.2-20070115cvs]                  WHATNOW(1)
2
3
4

NAME

6       whatnow - prompting front-end for sending messages
7

SYNOPSIS

9       whatnow [-draftfolder +folder] [-draftmessage msg] [-nodraftfolder]
10            [-editor editor] [-noedit] [-prompt string] [file] [-version]
11            [-help] [-attach header-field-name]
12

DESCRIPTION

14       Whatnow is the default program that queries the user about the disposi‐
15       tion of a composed draft.  It is normally automatically invoked by  one
16       of the nmh commands comp, dist, forw, or repl after the initial edit.
17
18       When  started,  the  editor  is started on the draft (unless -noedit is
19       given, in which case the initial edit is  suppressed).   Then,  whatnow
20       repetitively  prompts the user with “What now?”  and awaits a response.
21       The valid responses are:
22
23            edit             re-edit using the same editor that  was  used  on
24                             the   preceding  round  unless  a  profile  entry
25                             “<lasteditor>-next: <editor>” names an  alternate
26                             editor
27
28            edit <editor>    invoke <editor> for further editing
29
30            refile +folder   refile the draft into the given folder
31
32            mime             process  the draft as MIME composition file using
33                             the buildmimeproc command (mhbuild by default)
34
35            display          list the message being distributed/replied-to  on
36                             the terminal
37
38            list             list the draft on the terminal
39
40            send             send the message
41
42            send -watch      send the message and monitor the delivery process
43
44            push             send the message in the background
45
46            whom             list the addresses that the message will go to
47
48            whom -check      list  the  addresses  and  verify  that  they are
49                             acceptable to the transport service
50
51            quit             preserve the draft and exit
52
53            quit -delete     delete the draft and exit
54
55            delete           delete the draft and exit
56
57            cd directory     use the directory  when  interpreting  attachment
58                             file names
59
60            pwd              print the working directory for attachment files
61
62            ls [ls-options]  list  files  in  the attachment working directory
63                             using the ls command
64
65            attach files     add the named files to the draft as MIME  attach‐
66                             ments
67
68            alist [-ln]      list  the  MIME  attachments,  either short, long
69                             [-l] or numbered [-n]
70
71            detach [-n] files-or-numbers
72                             remove MIME attachments, either by file  name  or
73                             by number with -n
74
75       When  entering  your  response, you need only type enough characters to
76       uniquely identify the response.
77
78       For the edit response, any valid switch to the editor is valid.
79
80       For the send and push responses, any valid switch to send(1)  is  valid
81       (as push merely invokes send with the -push option).
82
83       For the whom response, any valid switch to whom(1) is valid.
84
85       For the refile response, any valid switch to the fileproc is valid.
86
87       For  the display and list responses, any valid argument to the lproc is
88       valid.  If any non-switch arguments are present, then the  pathname  of
89       the  draft  will  be excluded from the argument list given to the lproc
90       (this is useful for listing another nmh message).
91
92       See mh-profile(5) for further information about how editors are used by
93       nmh.  It also discusses how environment variables can be used to direct
94       whatnow's actions in complex ways.
95
96       The -prompt string switch sets the prompting string for whatnow.
97
98       The -draftfolder +folder and -draftmessage msg switches invoke the  nmh
99       draft  folder  facility.   This is an advanced (and highly useful) fea‐
100       ture.  Consult the mh-draft(5) man page for more information.
101
102

FILES

104       $HOME/.mh_profile          The user profile
105       <mh-dir>/draft             The draft file
106
107

PROFILE COMPONENTS

109       Path:                To determine the user's nmh directory
110       Draft-Folder:        To find the default draft-folder
111       Editor:              To override the default editor
112       <lasteditor>-next:   To name an editor to be used after exit
113                            from <lasteditor>
114       automimeproc:        If value is 1, and the draft is a MIME
115                            composition file, then automatically call
116                            buildmimeproc prior to sending.
117       buildmimeproc:       Program to translate MIME composition files
118       fileproc:            Program to refile the message
119       lproc:               Program to list the contents of a message
120       sendproc:            Program to use to send the message
121       whomproc:            Program to determine who a message would go to
122
123

SEE ALSO

125       send(1), whom(1)
126
127

DEFAULTS

129       `-prompt' defaults to “What Now? ”
130
131

CONTEXT

133       None
134
135

BUGS

137       The argument to the -prompt switch must  be  interpreted  as  a  single
138       token  by  the shell that invokes whatnow.  Therefore, one must usually
139       place the argument to this switch inside double-quotes.
140
141       If the initial edit fails, whatnow deletes your draft (by  renaming  it
142       with a leading comma); failure of a later edit preserves the draft.
143
144       If  the  buildmimeproc fails (returns a nonzero status), whatnow simply
145       prints a “What now?” prompt.  whatnow depends on the  buildmimeproc  to
146       tell the user that something went wrong.
147
148       If  whatnowproc  is  whatnow,  then  comp,  dist,  forw, and repl use a
149       built-in whatnow, and do not actually run the whatnow program.   Hence,
150       if  you  define  your  own  whatnowproc, don't call it whatnow since it
151       won't be run.
152
153       If sendproc is send, then whatnow uses a built-in  send,  it  does  not
154       actually run the send program.  Hence, if you define your own sendproc,
155       don't call it send since whatnow won't run it.
156
157
158
159MH.6.8                            1 Jul 2003                        WHATNOW(1)
Impressum