1 .TH BURST %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
6 burst \- explode digests into messages
13 .RB [ \-inplace " | " \-noinplace ]
14 .RB [ \-quiet " | " \-noquiet ]
15 .RB [ \-verbose " | " \-noverbose ]
21 considers the specified messages in the named folder to be
22 Internet digests, and explodes them in that folder.
26 is given, each digest is replaced by the \*(lqtable
27 of contents\*(rq for the digest (the original digest is removed).
29 then renumbers all of the messages following the digest in the
30 folder to make room for each of the messages contained within the digest.
31 These messages are placed immediately after the digest.
35 is given, each digest is preserved, no table of contents
36 is produced, and the messages contained within the digest are placed at
37 the end of the folder. Other messages are not tampered with in any way.
43 to be silent about reporting
44 messages that are not in digest format.
50 to tell the user the general
51 actions that it is taking to explode the digest.
55 works equally well on forwarded messages
56 and blind\-carbon\-copies as on Internet digests, provided that the
57 former two were generated by
64 .ta \w'%etcdir%/ExtraBigFileName 'u
65 ^$HOME/\&.mh\(ruprofile~^The user profile
67 .SH "PROFILE COMPONENTS"
71 .ta \w'ExtraBigProfileName 'u
72 ^Path:~^To determine the user's nmh directory
73 ^Current\-Folder:~^To find the default current folder
74 ^Msg\-Protect:~^To set mode when creating a new message
77 inc(1), msh(1), pack(1),
78 .I "Proposed Standard for Message Encapsulation"
82 .RB ` +folder "' defaults to the current folder"
83 .RB ` msgs "' defaults to cur"
89 If a folder is given, it will become the current folder. If
91 is given, then the first message burst becomes the current message.
92 This leaves the context ready for a
94 of the table of contents
97 to see the first message of the digest. If
99 is given, then the first message extracted from the
100 first digest burst becomes the current message. This leaves the context
101 in a similar, but not identical, state to the context achieved when using
106 program enforces a limit on the number of messages which
109 from a single message. This number is on the order
110 of 1000 messages. There is usually no limit on the number of messages
111 which may reside in the folder after the
116 uses a sophisticated algorithm to determine where
117 one encapsulated message ends and another begins, not all digestifying
118 programs use an encapsulation algorithm. In degenerate cases, this
121 finding an encapsulation boundary
122 prematurely and splitting a single encapsulated message into two or
123 more messages. These erroneous digestifying programs should be fixed.
125 Furthermore, any text which appears after the last encapsulated message
126 is not placed in a separate message by
129 digestified messages, this text is usually an \*(lqEnd of digest\*(rq
130 string. As a result of this possibly un\-friendly behavior on the
136 this trailing information is lost. In practice, this is not a problem
137 since correspondents usually place remarks in text prior to the first
138 encapsulated message, and this information is not lost.