5 .TH MH-DRAFT %manext5% "%nmhdate%" MH.6.8 [%nmhversion%]
7 mh-draft \- draft folder facility for nmh message system
13 There are a number of interesting advanced facilities for the composition of
16 .SS "The Draft Folder"
23 commands have two additional switches,
29 which allow you to manipulate the various draft messages you are composing.
34 is used, these commands are
35 directed to construct a draft message in the indicated folder.
37 .RI \*(lq Draft\-Folder \*(rq
38 profile entry may be used to declare a default draft folder for use with
48 is given, the specified draft is used to compose the message. If
52 draft defaults to `new' (create a new draft) unless the user invokes
56 in which case the default is `cur'.
58 Hence, the user may have several message compositions in progress
59 simultaneously. Now, all of the
61 tools are available on each of the user's message drafts (e.g.
65 and so on). If the folder does not exist, the user is asked if it should be
66 created (just like with
68 Also, the last draft message
69 the user was composing is known as `cur' in the draft folder.
73 command has these switches as well. Hence,
74 from the shell, the user can send off whatever drafts desired using the
77 `msgs' convention with
80 If no `msgs' are given, it defaults to `cur'.
82 In addition, all five programs have a
84 switch, which undoes the last occurrence of
87 (useful if the latter occurs in the user's
91 If the user does not give the
94 switch, then all these commands act \*(lqnormally\*(rq. Note that the
100 still refers to the file called `draft' in the user's
102 directory. In the interests of economy of expression, when using
106 the user needn't prefix the draft `msg' or `msgs' with
109 commands accept a `file' or `files' argument, and they will, if given
112 treat these arguments as `msg' or `msgs'. (This may appear to be
113 inconsistent, at first, but it saves a lot of typing) Hence,
117 send -draftfolder +drafts first
125 send -draftfolder +drafts -draftmessage first
129 To make all this a bit more clear, here are some examples. Let's assume
130 that the following entries are in the
136 Draft\-Folder: +drafts
137 sendf: \-draftfolder +drafts
141 Furthermore, let's assume that the program
143 is a (symbolic) link in the user's
147 Then, any of the commands
158 constructs the message draft in the `draft' folder using the `new'
159 message number. Furthermore, they each define `cur' in this folder to
160 be that message draft. If the user were to use the
162 option at `What now?' level, then later on, if no other draft composition
163 was done, the draft could be sent with simply
171 Or, if more editing was required, the draft could be edited with
179 Instead, if other drafts had been composed in the meantime, so that this
180 message draft was no longer known as `cur' in the `draft' folder, then
183 the folder to see which message draft in the
184 folder should be used for editing or sending. Clever users could even
191 comp -use `pick +drafts -to nmh-workers`
199 sendf `pick +drafts -to nmh-workers`
205 example, the output from
207 must resolve to a single message draft (it makes no sense to talk about
208 composing two or more drafts with one invocation of
212 example, as many message drafts as desired can appear, since
214 doesn't mind sending more than one draft at a time.
216 Note that the argument
219 is not included in the profile entry for
225 directly, they supply
227 with the UNIX pathname of the message draft, and
234 is concerned, a draft folder is not being used.
236 It is important to realize that
238 treats the draft folder like a standard
240 folder in nearly all respects. There are two exceptions:
242 First, under no circumstancs will the
245 switch cause the named folder to become the current folder.
247 Obviously, if the folder appeared in the context of a standard
259 it might become the current folder, depending on the context changes of the
263 Second, although conceptually
265 deletes the `msgs' named in the draft folder, it does not call
267 to perform the deletion.
269 .SS "What Happens if the Draft Exists"
277 are invoked and the draft you indicated already exists, these programs
278 will prompt the user for a reponse directing the program's action.
283 Draft ``/home/foobar/nmhbox/draft'' exists (xx bytes).
288 The appropriate responses and their meanings are:
294 .BR ^replace~^ "- deletes the draft and starts afresh"
295 .BR ^list~^ "- lists the draft"
296 .BR ^refile~^ "- files the draft into a folder and starts afresh"
297 .BR ^quit~^ "- leaves the draft intact and exits"
301 In addition, if you specified
304 to the command, then one other response will be accepted:
310 .BR ^new~^ "- finds a new draft"
320 command will accept one more response:
326 .BR ^use~^ "- re-uses the draft"
projects / mmh / blob