5 .TH BURST %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
7 burst \- explode digests into messages
13 .RB [ \-inplace " | " \-noinplace ]
14 .RB [ \-quiet " | " \-noquiet ]
15 .RB [ \-verbose " | " \-noverbose ]
20 considers the specified messages in the named folder to be
21 Internet digests, and explodes them in that folder.
25 is given, each digest is replaced by the \*(lqtable
26 of contents\*(rq for the digest (the original digest is removed).
28 then renumbers all of the messages following the digest in the
29 folder to make room for each of the messages contained within the digest.
30 These messages are placed immediately after the digest.
34 is given, each digest is preserved, no table of contents
35 is produced, and the messages contained within the digest are placed at
36 the end of the folder. Other messages are not tampered with in any way.
42 to be silent about reporting
43 messages that are not in digest format.
49 to tell the user the general
50 actions that it is taking to explode the digest.
54 works equally well on forwarded messages
55 and blind\-carbon\-copies as on Internet digests, provided that the
56 former two were generated by
64 .ta \w'/usr/local/nmh/etc/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 .IR "Proposed Standard for Message Encapsulation" " (RFC\-934)"
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
107 program enforces a limit on the number of messages which
110 from a single message. This number is on the order
111 of 1000 messages. There is usually no limit on the number of messages
112 which may reside in the folder after the
117 uses a sophisticated algorithm to determine where
118 one encapsulated message ends and another begins, not all digestifying
119 programs use an encapsulation algorithm. In degenerate cases, this
122 finding an encapsulation boundary
123 prematurely and splitting a single encapsulated message into two or
124 more messages. These erroneous digestifying programs should be fixed.
126 Furthermore, any text which appears after the last encapsulated message
127 is not placed in a separate message by
130 digestified messages, this text is usually an \*(lqEnd of digest\*(rq
131 string. As a result of this possibly un\-friendly behavior on the
137 this trailing information is lost. In practice, this is not a problem
138 since correspondents usually place remarks in text prior to the first
139 encapsulated message, and this information is not lost.