1BURST(1) General Commands Manual BURST(1)
2
6 burst - explode digests into nmh messages
7
9 burst [-help] [-version] [+folder] [msgs] [-inplace | -noinplace]
10 [-mime | -nomime] [-automime] [-quiet | -noquiet] [-verbose |
11 -noverbose]
12
14 burst considers the specified messages in the named folder to be Inter‐
15 net digests, and explodes them in that folder.
16 If -inplace is given, each digest is replaced by its “table of con‐
18 tents” and the digest is removed. burst then renumbers the messages
19 which follow the digest, in the folder, making room for each of the
20 exploded messages, which are placed immediately after the “table of
21 contents”.
22 If -noinplace is given, each digest is preserved, no table of contents
24 is produced, and the exploded messages are placed at the end of the
25 folder. Other messages in the folder are not affected.
26 If -automime is given, burst will try to determine if the message is
28 formatted with MIME and contains MIME parts of type “message/rfc822”.
29 If it does, it will burst the message using MIME formatting rules. The
30 -mime switch can be used to enforce the use of MIME formatting. The
31 -nomime switch will force burst to use RFC 934 rules.
32 The -quiet switch directs burst to be silent about reporting messages
34 that are not in digest format.
35 The -verbose switch directs burst to tell the user the general actions
37 that it is taking to explode the digest.
38 It turns out that burst works equally well on forwarded messages and
40 blind-carbon-copies as on Internet digests, provided that the former
41 were generated by forw or send.
42
44 $HOME/.mh_profile The user's profile.
45
47 Path: To determine the user's nmh directory.
48 Current-Folder: To find the default current folder.
49 Msg-Protect: To set mode when creating a new message.
50
52 inc(1), pack(1)
53 Proposed Standard for Message Encapsulation (RFC 934)
55
57 +folder The current folder.
58 msgs The current message.
59 -noinplace
60 -automime
61 -noquiet
62 -noverbose
63
65 If a folder is given, it will become the current folder. If -inplace
66 is given, then the first message burst becomes the current message.
67 This leaves the context ready for a show of the table of contents of
68 the digest, and a next to see the first message of the digest. If
69 -noinplace is given, then the first message extracted from the first
70 digest burst becomes the current message. This leaves the context in a
71 similar, but not identical, state to the context achieved when using
72 -inplace.
73
75 The burst program enforces a limit of approximately 1,000 on the number
76 of messages which may be burst from a single message. There is usually
77 no limit on the number of messages which may reside in the folder after
78 the bursting.
79 Although burst uses a sophisticated algorithm to determine where one
81 encapsulated message ends and another begins, not all digestifying pro‐
82 grams use an encapsulation algorithm. In degenerate cases, this usu‐
83 ally results in burst finding an encapsulation boundary prematurely and
84 splitting a single encapsulated message into two or more messages.
85 These erroneous digestifying programs should be fixed.
86 Furthermore, any text which appears after the last encapsulated message
88 is not placed in a separate message by burst. In the case of digesti‐
89 fied messages, this text is usually an “End of digest” string. As a
90 result of this possibly unfriendly behavior on the part of burst, note
91 that when the -inplace option is used, this trailing information is
92 lost. In practice, this is not a problem since correspondents usually
93 place remarks in text prior to the first encapsulated message, and this
94 information is not lost.
95nmh-1.7.1 2013-02-08 BURST(1)