10 date 90.04.05.15.12.10; author sources; state Exp;
15 date 90.03.22.11.31.00; author sources; state Exp;
20 date 90.03.20.19.41.36; author sources; state Exp;
25 date 90.03.20.17.35.54; author sources; state Exp;
30 date 90.03.20.17.20.43; author sources; state Exp;
48 burst \- explode digests into messages
52 \%[\-inplace] \%[\-noinplace]
53 \%[\-quiet] \%[\-noquiet]
54 \%[\-verbose] \%[\-noverbose]
57 \fIBurst\fR considers the specified messages in the named folder to be
58 Internet digests, and explodes them in that folder.
60 If `\-inplace' is given,
61 each digest is replaced by the \*(lqtable of contents\*(rq for the digest
62 (the original digest is removed).
63 \fIBurst\fR then renumbers all of the messages following the digest in the
64 folder to make room for each of the messages contained within the digest.
65 These messages are placed immediately after the digest.
67 If `\-noinplace' is given,
68 each digest is preserved,
69 no table of contents is produced,
70 and the messages contained within the digest are placed at the end of
72 Other messages are not tampered with in any way.
74 The `\-quiet' switch directs \fIburst\fR to be silent about reporting
75 messages that are not in digest format.
77 The `\-verbose' switch directs \fIburst\fR to tell the user the general
78 actions that it is taking to explode the digest.
80 It turns out that \fIburst\fR works equally well on forwarded messages and
81 blind\-carbon\-copies as on Internet digests,
82 provided that the former two were generated by \fIforw\fR or \fIsend\fR.
84 ^$HOME/\&.mh\(ruprofile~^The user profile
86 ^Path:~^To determine the user's MH directory
88 ^Current\-Folder:~^To find the default current folder
90 ^Msg\-Protect:~^To set mode when creating a new message
92 \fIProposed Standard for Message Encapsulation\fR (aka RFC\-934),
94 inc(1), msh(1), pack(1)
96 `+folder' defaults to the current folder
98 `msgs' defaults to cur
106 If a folder is given, it will become the current folder.
107 If `\-inplace' is given,
108 then the first message burst becomes the current message.
109 This leaves the context ready for a \fIshow\fR of the table of contents
110 of the digest, and a \fInext\fR to see the first message of the digest.
111 If `\-noinplace' is given,
112 then the first message extracted from the first digest burst becomes the
114 This leaves the context in a similar, but not identical,
115 state to the context achieved when using `\-inplace'.
117 The \fIburst\fR program enforces a limit on the number of messages which may
118 be \fIburst\fR from a single message.
119 This number is on the order of 1000 messages.
120 There is usually no limit on the number of messages which may reside in the
121 folder after the \fIburst\fRing.
123 Although \fIburst\fR uses a sophisticated algorithm to determine where one
124 encapsulated message ends and another begins,
125 not all digestifying programs use an encapsulation algorithm.
127 this usually results in \fIburst\fR finding an encapsulation boundary
128 prematurely and splitting a single encapsulated message into two or more
130 These erroneous digestifying programs should be fixed.
133 any text which appears after the last encapsulated message is not placed
134 in a seperate message by \fIburst\fR.
135 In the case of digestified messages,
136 this text is usally an \*(lqEnd of digest\*(rq string.
137 As a result of this possibly un\-friendly behavior on the part of \fIburst\fR,
138 note that when the `\-inplace' option is used,
139 this trailing information is lost.
141 this is not a problem since correspondents usually place remarks in text
142 prior to the first encapsulated message,
143 and this information is not lost.
150 @put things back, do .NA stuff another way
164 .TH BURST 1 @@(MHCENTERFOOT) @@(MHLEFTFOOT)
174 @fixup for makewhatis
179 .TH BURST 1 [mh.6] MH