8 date 92.10.16.21.36.02; author jromine; state Exp;
13 date 90.12.18.14.40.06; author mh; state Exp;
18 date 90.04.05.15.08.44; author sources; state Exp;
23 date 90.03.23.15.03.30; author sources; state Exp;
28 date 90.03.23.14.57.30; author sources; state Exp;
33 date 90.03.22.11.31.07; author sources; state Exp;
38 date 90.03.20.19.41.45; author sources; state Exp;
43 date 90.03.20.17.36.01; author sources; state Exp;
48 date 90.03.16.14.28.23; author sources; state Exp;
53 date 90.02.07.13.15.02; author sources; state Exp;
58 date 90.02.07.13.05.39; author sources; state Exp;
73 .\" @@(#)$Id: forw.rf,v 1.10 1990/12/18 14:40:06 mh Exp jromine $
76 forw \- forward messages
80 \%[\-annotate] \%[\-noannotate]
81 \%[\-draftfolder\ +folder] \%[\-draftmessage\ msg] \%[\-nodraftfolder]
82 \%[\-editor\ editor] \%[\-noedit]
83 \%[\-filter\ filterfile]
85 \%[\-format] \%[\-noformat]
86 \%[\-inplace] \%[\-noinplace]
88 \%[\-mime] \%[\-nomime]
90 \%[\-whatnowproc\ program] \%[\-nowhatnowproc]
96 \%[\-digest\ list] \%[\-issue\ number] \%[\-volume\ number]
97 \%[other\ switches\ for\ \fIforw\fR]
100 \fIForw\fR may be used to prepare a message containing other
102 It constructs the new message from the components file
103 or `\-form\ formfile' (see \fIcomp\fR\0), with a body composed of the
104 message(s) to be forwarded.
105 An editor is invoked as in \fIcomp\fR,
106 and after editing is complete, the user is prompted before the message
109 The default message form contains the following elements:
115 .so @@(MHETCPATH)/forwcomps
120 If the file named \*(lqforwcomps\*(rq exists in the user's MH directory,
121 it will be used instead of this form.
122 In either case, the file specified by `\-form\ formfile' will be
125 If the draft already exists,
126 \fIforw\fR will ask you as to the disposition of the draft.
127 A reply of \fBquit\fR will abort \fIforw\fR, leaving the draft intact;
128 \fBreplace\fR will replace the existing draft with a blank skeleton;
129 and \fBlist\fR will display the draft.
131 If the `\-annotate' switch is given, each message being
132 forwarded will be annotated with the lines
137 where each address list contains as many lines as required.
139 will be done only if the message is sent directly from \fIforw\fR.
140 If the message is not sent immediately from \fIforw\fR,
141 \*(lqcomp\ \-use\*(rq may be used to re\-edit and send the constructed message,
143 the annotations won't take place.
144 The '\-inplace' switch causes annotation to
145 be done in place in order to preserve links to the annotated message.
147 See \fIcomp\fR\0(1) for a description of the `\-editor' and `\-noedit'
150 Although \fIforw\fR uses the `\-form\ formfile' switch to direct it how to
151 construct the beginning of the draft, the `\-filter\ filterfile',
152 `\-format', and `\-noformat'
153 switches direct \fIforw\fR as to how each forwarded message should be
154 formatted in the body of the draft.
155 If `\-noformat' is specified,
156 then each forwarded message is output exactly as it appears.
157 If `\-format' or `\-filter\ filterfile' is specified,
158 then each forwarded message is filtered (re\-formatted) prior to being
159 output to the body of the draft.
160 The filter file for \fIforw\fR should be a standard form file for
162 as \fIforw\fR will invoke \fImhl\fR to format the forwarded messages.
163 The default message filter (what you get with `\-format') is:
169 .so @@(MHETCPATH)/mhl.forward
174 If the file named \*(lqmhl.forward\*(rq exists in the user's MH directory,
175 it will be used instead of this form.
176 In either case, the file specified by `\-filter\ filterfile' will be
179 `\-noformat' will reproduce each forwarded message exactly,
180 `\-format' will use \fImhl\fR and a default filterfile, \*(lqmhl.forward\*(rq,
181 to format each forwarded message, and
182 `\-filter\ filterfile' will use the named filterfile to format each
183 forwarded message with \fImhl\fR.
185 Each forwarded message is separated with an encapsulation delimiter
187 dashes in the first column of the forwarded messages will be prepended
189 when received, the message is suitable for bursting by \fIburst\fR\0(1).
190 This follows the Internet RFC\-934 guidelines.
192 For users of \fIprompter\fR\0(1), by specifying prompter's `-prepend'
193 switch in the \&.mh\(ruprofile file, any commentary text is entered before
194 the forwarded messages. (A major win!)
197 To use the MIME rules for encapsulation,
198 specify the `\-mime' switch.
199 This directs \fIforw\fR to generate an \fImhn\fR composition file.
200 Note that MH will not invoke \fImhn\fR automatically,
201 unless you add this line to your \&.mh\(ruprofile file:
208 you must specifically give the command
214 prior to sending the draft.
216 To automate this somewhat,
217 create a link to \fIprompter\fR called \fIrapid\fR
218 and put these lines in your \&.mh\(ruprofile file:
222 forw: -editor rapid -mime
236 Subject: \fIwhatever\fR
238 --------Enter initial text
240 \fIblah, blah, blah.\fR
250 The \fIedit\fR command invokes \fImhn\fR automatically.
253 The `\-draftfolder\ +folder' and `\-draftmessage\ msg' switches invoke the
254 \fIMH\fR draft folder facility.
255 This is an advanced (and highly useful) feature.
256 Consult the \fBAdvanced Features\fR section of the \fIMH\fR manual for more
259 Upon exiting from the editor,
260 \fIforw\fR will invoke the \fIwhatnow\fR program.
261 See \fIwhatnow\fR\0(1) for a discussion of available options.
262 The invocation of this program can be inhibited by using the `\-nowhatnowproc'
265 it is the \fIwhatnow\fR program which starts the initial edit.
266 Hence, `\-nowhatnowproc' will prevent any edit from occurring.)
268 The `\-digest\ list', `\-issue\ number', and `\-volume\ number' switches
269 implement a digest facility for \fIMH\fR. Specifying these switches
270 enables and/or overloads the following escapes:
273 .ta \w'Component 'u +\w'Escape 'u +\w'Returns 'u
274 \fIType\fR \fIEscape\fR \fIReturns\fR \fIDescription\fR
275 \fIcomponent\fR \fIdigest\fR string Argument to `\-digest'
276 \fIfunction\fR \fIcur\fR integer Argument to `\-volume'
277 \fIfunction\fR \fImsg\fR integer Argument to `\-issue'
281 Consult the \fBAdvanced Features\fR section of
282 the \fIMH\fR User's Manual for more information on making digests.
284 ^@@(MHETCPATH)/forwcomps~^The message skeleton
285 ^or <mh\-dir>/forwcomps~^Rather than the standard skeleton
286 ^@@(MHETCPATH)/digestcomps~^The message skeleton if `\-digest' is given
287 ^or <mh\-dir>/digestcomps~^Rather than the standard skeleton
288 ^@@(MHETCPATH)/mhl.forward~^The message filter
289 ^or <mh\-dir>/mhl.forward~^Rather than the standard filter
290 ^$HOME/\&.mh\(ruprofile~^The user profile
291 ^<mh\-dir>/draft~^The draft file
293 ^Path:~^To determine the user's MH directory
295 ^Current\-Folder:~^To find the default current folder
297 ^Draft\-Folder:~^To find the default draft\-folder
299 ^Editor:~^To override the default editor
301 ^Msg\-Protect:~^To set mode when creating a new message (draft)
303 ^fileproc:~^Program to refile the message
305 ^mhlproc:~^Program to filter messages being forwarded
307 ^whatnowproc:~^Program to ask the \*(lqWhat now?\*(rq questions
309 \fIProposed Standard for Message Encapsulation\fR (aka RFC\-934),
311 comp(1), dist(1), repl(1), send(1), whatnow(1), mh\-format(5)
313 `+folder' defaults to the current folder
314 `msgs' defaults to cur
328 If a folder is given, it will become the current folder.
329 The first message forwarded will become the current message.
331 If \fIwhatnowproc\fR is \fIwhatnow\fR,
332 then \fIforw\fR uses a built\-in \fIwhatnow\fR,
333 it does not actually run the \fIwhatnow\fR program.
334 Hence, if you define your own \fIwhatnowproc\fR,
335 don't call it \fIwhatnow\fR since \fIforw\fR won't run it.
337 When \fIforw\fR is told to annotate the messages it forwards,
338 it doesn't actually annotate them until the draft is successfully sent.
339 If from the \fIwhatnowproc\fR,
340 you \fIpush\fR instead of \fIsend\fR,
341 it's possible to confuse \fIforw\fR by re\-ordering the file
342 (e.g., by using `folder\0\-pack') before the message is successfully sent.
343 \fIDist\fR and \fIrepl\fR don't have this problem.
345 To avoid prepending the leading dash characters in forwarded messages,
346 there is a `\-nodashmunging' option. See the \*(lqHidden Features\*(rq
347 section of the \fIMH Administrator's Guide\fR for more details.
354 @mention -nodashmunging
360 .\" @@(#)$Id: forw.rf,v 1.9 90/04/05 15:08:44 sources Exp Locker: mh $
382 @ make -[no]dashmunging hidden
395 \%[\-dashmunging] \%[\-nodashmunging]
397 Specifying `\-nodashmunging' will inhibit prepending the leading
398 dash and space characters, but this may confuse later bursters.
407 @put things back, do .NA stuff another way
412 enables the following additional \fIcomponent\fR escapes:
415 .ta \w'Escape 'u +\w'Returns 'u
416 \fIEscape\fR \fIReturns\fR \fIDescription\fR
417 \fIdigest\fR string Argument specified with `\-digest'
418 \fIissue\fR integer Argument specified with `\-issue'
419 \fIvolume\fR integer Argument specified with `\-volume'
430 .TH FORW 1 @@(MHCENTERFOOT) @@(MHLEFTFOOT)
440 @fixup for makewhatis
466 @document -[no]dashmunging
471 implement a digest facility for \fIMH\fR.
472 See the \fIMH\fR user's manual for more information.
475 comp(1), dist(1), repl(1), send(1), whatnow(1)
487 Each forwarded message is separated with an encapsulation delimiter so that