| rev |
line source |
|
meillo@0
|
1 .H0 "Work Report
|
|
meillo@0
|
2 .P
|
|
meillo@0
|
3 foo
|
|
meillo@0
|
4 .P
|
|
meillo@0
|
5 bar
|
|
meillo@0
|
6
|
|
meillo@12
|
7 .H1 "Removal of Code Relicts
|
|
meillo@0
|
8 .P
|
|
meillo@20
|
9 The code base of mmh originates from the late 70s, had been extensively
|
|
meillo@12
|
10 worked on in the mid 80s, and had been partly reorganized and extended
|
|
meillo@12
|
11 in the 90s. Relicts of all those times had gathered in the code base.
|
|
meillo@12
|
12 My goal was to remove any ancient code parts. One part of the task was
|
|
meillo@12
|
13 converting obsolete code constructs to standard constructs, the other part
|
|
meillo@12
|
14 was dropping obsolete functions.
|
|
meillo@12
|
15 .P
|
|
meillo@12
|
16 As I'm not even thirty years old and have no more than seven years of
|
|
meillo@12
|
17 Unix experience, I needed to learn about the history in retroperspective.
|
|
meillo@12
|
18 Older people likely have used those ancient constructs themself
|
|
meillo@12
|
19 and have suffered from their incompatiblities and have longed for
|
|
meillo@12
|
20 standardization. Unfortunately, I have only read that others had done so.
|
|
meillo@12
|
21 This put me in a much more difficult positions when working on the old
|
|
meillo@12
|
22 code. I needed to recherche what other would have known by heart from
|
|
meillo@12
|
23 experience. All my programming experience comes from a time past ANSI C
|
|
meillo@12
|
24 and past POSIX. Although I knew about the times before, I took the
|
|
meillo@12
|
25 current state implicitely for granted most of the time.
|
|
meillo@12
|
26 .P
|
|
meillo@12
|
27 Being aware of
|
|
meillo@12
|
28 these facts, I rather let people with more historic experience solve the
|
|
meillo@12
|
29 task of converting the ancient code constructs to standardized ones.
|
|
meillo@12
|
30 Luckily, Lyndon Nerenberg focused on this task at the nmh project.
|
|
meillo@12
|
31 He converted large parts of the code to POSIX constructs, removing
|
|
meillo@12
|
32 the conditionals compilation for now standardized features.
|
|
meillo@12
|
33 I'm thankful for this task being solved. I only pulled the changes into
|
|
meillo@12
|
34 mmh.
|
|
meillo@12
|
35 .P
|
|
meillo@20
|
36 The other task \(en dropping ancient functionality to remove old code \(en
|
|
meillo@12
|
37 I did myself, though. My position to strip mmh to the bare minimum of
|
|
meillo@12
|
38 frequently used features is much more revolutional than the nmh community
|
|
meillo@20
|
39 likes it. Without the need to justify my decisions, I was able to quickly
|
|
meillo@20
|
40 remove functionality I considered ancient.
|
|
meillo@20
|
41 The need to discuss my decisions with
|
|
meillo@20
|
42 peers likely would have slowed this process down. Of course, I researched
|
|
meillo@12
|
43 if a particular feature really should be dropped. Having not had any
|
|
meillo@12
|
44 contact to this feature within my computer life was a first indicator to
|
|
meillo@12
|
45 drop it, but I also asked others and searched the literature for modern
|
|
meillo@12
|
46 usage of the feature. If it appeared to be truly ancient, I dropped it.
|
|
meillo@12
|
47 The reason for dropping is always part of the commit message in the
|
|
meillo@12
|
48 version control system. Thus, it is easy for others to check their
|
|
meillo@12
|
49 view on the topic with mine and possibly to argue for reinclusion.
|
|
meillo@12
|
50
|
|
meillo@12
|
51 .U2 "MMDF maildrop support
|
|
meillo@12
|
52 .P
|
|
meillo@12
|
53 I did drop any support for the MMDF maildrop format. This type of format
|
|
meillo@12
|
54 is conceptionally similar to the mbox format, but uses four bytes with
|
|
meillo@12
|
55 value 1 (\fL^A^A^A^A\fP) as message delimiter,
|
|
meillo@18
|
56 instead of the string ``\fLFrom\ \fP''.
|
|
meillo@12
|
57 Due to the similarity and mbox being the de-facto standard maildrop
|
|
meillo@12
|
58 format on Unix, but also due to the larger influence of Sendmail than MMDF,
|
|
meillo@12
|
59 the MMDF maildrop format had vanished.
|
|
meillo@12
|
60 .P
|
|
meillo@12
|
61 The simplifications within the code were only moderate. Switches could
|
|
meillo@12
|
62 be removed from tools like
|
|
meillo@12
|
63 .L packf ,
|
|
meillo@12
|
64 which generate packed mailboxes. Only one packed mailbox format remained:
|
|
meillo@12
|
65 mbox.
|
|
meillo@12
|
66 The most important changes affect the equally named mail parsing routine in
|
|
meillo@12
|
67 .L sbr/m_getfld.c .
|
|
meillo@12
|
68 The direct MMDF code had been removed, but as now only one packed mailbox
|
|
meillo@12
|
69 format is left, code structure simplifications are likely possible.
|
|
meillo@12
|
70 The reason why they are still outstanding is the heavily optimized code
|
|
meillo@18
|
71 of
|
|
meillo@18
|
72 .Fu m_getfld() .
|
|
meillo@18
|
73 Changes beyond a small local scope \(en
|
|
meillo@12
|
74 which restructuring in its core is \(en cause a high risk of damaging
|
|
meillo@12
|
75 the intricate workings of the optimized code. This problem is know
|
|
meillo@12
|
76 to the developers of nmh, too. They also avoid touching this minefield
|
|
meillo@12
|
77 if possible.
|
|
meillo@12
|
78
|
|
meillo@12
|
79 .U2 "UUCP Bang Paths
|
|
meillo@12
|
80 .P
|
|
meillo@12
|
81 More questionably than the former topic is the removal of support for the
|
|
meillo@12
|
82 UUCP bang path address style. However, the user may translate the bang
|
|
meillo@12
|
83 paths on retrieval to Internet addresses and the other way on posting
|
|
meillo@12
|
84 messages. The former can be done my an MDA like procmail; the latter
|
|
meillo@12
|
85 by a sendmail wrapper. This would ensure that any address handling would
|
|
meillo@12
|
86 work as expected. However, it might just work well without any
|
|
meillo@12
|
87 such modifications, as mmh does not touch addresses much, in general.
|
|
meillo@12
|
88 But I can't ensure as I have never used an environment with bang paths.
|
|
meillo@12
|
89 Also, the behavior might break at any point in further development.
|
|
meillo@12
|
90
|
|
meillo@12
|
91 .U2 "Hardcopy terminal support
|
|
meillo@12
|
92 .P
|
|
meillo@12
|
93 More of a funny anecdote is the remaining of a check for printing to a
|
|
meillo@12
|
94 hardcopy terminal until Spring 2012, when I finally removed it.
|
|
meillo@12
|
95 I surely would be very happy to see such a terminal in action, maybe
|
|
meillo@12
|
96 actually being able to work on it, but I fear my chances are null.
|
|
meillo@12
|
97 .P
|
|
meillo@12
|
98 The check only prevented a pager to be placed between the outputting
|
|
meillo@18
|
99 program (\c
|
|
meillo@18
|
100 .Pn mhl )
|
|
meillo@18
|
101 and the terminal. This could have been ensured with
|
|
meillo@18
|
102 the
|
|
meillo@18
|
103 .Sw \-nomoreproc
|
|
meillo@18
|
104 at the command line statically, too.
|
|
meillo@12
|
105
|
|
meillo@12
|
106 .U2 "Removed support for header fields
|
|
meillo@12
|
107 .P
|
|
meillo@12
|
108 The `Encrypted' header had been introduced by RFC\^822, but already
|
|
meillo@12
|
109 marked legacy in RFC 2822. It was superseded by FIXME.
|
|
meillo@12
|
110 Mmh does no more support this header.
|
|
meillo@12
|
111 .P
|
|
meillo@21
|
112 Native support for `Face' headers
|
|
meillo@21
|
113 had been removed, as well.
|
|
meillo@21
|
114 The feature is similar to the `X-Face' header in its intent,
|
|
meillo@21
|
115 but takes a different approach to store the image.
|
|
meillo@21
|
116 Instead of encoding the image data directly into the header,
|
|
meillo@21
|
117 the the header contains the hostname and UDP port where the image
|
|
meillo@21
|
118 date could be retrieved.
|
|
meillo@21
|
119 Neither `X-Face' nor the here described `Face' system
|
|
meillo@21
|
120 \**
|
|
meillo@21
|
121 .FS
|
|
meillo@21
|
122 There is also a newer but different system, invented 2005,
|
|
meillo@21
|
123 using `Face' headers.
|
|
meillo@21
|
124 It is the successor of `X-Face' providing colored PNG images.
|
|
meillo@21
|
125 .FE
|
|
meillo@21
|
126 became well used in the large scale.
|
|
meillo@21
|
127 It's still possible to use a Face systems,
|
|
meillo@21
|
128 although mmh does not provide support for any of the different systems
|
|
meillo@21
|
129 anymore. It's fairly easy to write a small shell script to
|
|
meillo@21
|
130 extract the embedded or fetch the external Face data and display the image.
|
|
meillo@21
|
131 Own Face headers can be added into the draft template files.
|
|
meillo@21
|
132 .P
|
|
meillo@12
|
133 `Content-MD5' headers were introduced by RFC\^1864. They provide only
|
|
meillo@12
|
134 a verification of data corruption during the transfer. By no means can
|
|
meillo@12
|
135 they ensure verbatim end-to-end delivery of the contents. This is clearly
|
|
meillo@12
|
136 stated in the RFC. The proper approach to provide verificationability
|
|
meillo@12
|
137 of content in an end-to-end relationship is the use of digital cryptography
|
|
meillo@12
|
138 (RFCs FIXME). On the other hand, transfer protocols should ensure the
|
|
meillo@12
|
139 integrity of the transmission. In combinations these two approaches
|
|
meillo@12
|
140 make the `Content-MD5' header field useless. In consequence, I removed
|
|
meillo@12
|
141 the support for it. By this removal, MD5 computation is not needed
|
|
meillo@12
|
142 anywhere in mmh. Hence, over 500 lines of code were removed by this one
|
|
meillo@12
|
143 change. Even if the `Content-MD5' header field is useful sometimes,
|
|
meillo@12
|
144 I value its usefulnes less than the improvement in maintainability, caused
|
|
meillo@12
|
145 by the removal.
|
|
meillo@12
|
146
|
|
meillo@20
|
147 .U2 "Prompter's Control Keys
|
|
meillo@20
|
148 .P
|
|
meillo@20
|
149 The program
|
|
meillo@20
|
150 .Pn prompter
|
|
meillo@20
|
151 queries the user to fill in a message form. When used by
|
|
meillo@20
|
152 .Pn comp
|
|
meillo@20
|
153 as:
|
|
meillo@20
|
154 .DS
|
|
meillo@20
|
155 comp \-editor prompter
|
|
meillo@20
|
156 .DE
|
|
meillo@20
|
157 the resulting behavior is similar to
|
|
meillo@20
|
158 .Pn mailx .
|
|
meillo@20
|
159 Appearently,
|
|
meillo@20
|
160 .Pn prompter
|
|
meillo@20
|
161 hadn't been touched lately. Otherwise it's hardly explainable why it
|
|
meillo@20
|
162 still offered the switches
|
|
meillo@20
|
163 .Sn \-erase \fUchr\fP
|
|
meillo@20
|
164 and
|
|
meillo@20
|
165 .Sn \-kill \fUchr\fP
|
|
meillo@20
|
166 to name the characters for command line editing.
|
|
meillo@21
|
167 The times when this had been necessary are long time gone.
|
|
meillo@20
|
168 Today these things work out-of-the-box, and if not, are configured
|
|
meillo@20
|
169 with the standard tool
|
|
meillo@20
|
170 .Pn stty .
|
|
meillo@20
|
171
|
|
meillo@21
|
172 .U2 "Vfork and Retry Loops
|
|
meillo@21
|
173 .P
|
|
meillo@21
|
174 MH creates many processes, which is a concequence of the toolchest approach.
|
|
meillo@21
|
175 In earlier times
|
|
meillo@21
|
176 .Fu fork()
|
|
meillo@21
|
177 had been an expensive system call, as the process's whole image needed
|
|
meillo@21
|
178 to be duplicated. One common case is replacing the image with
|
|
meillo@21
|
179 .Fu exec()
|
|
meillo@21
|
180 right after having forked the child process.
|
|
meillo@21
|
181 To speed up this case, the
|
|
meillo@21
|
182 .Fu vfork()
|
|
meillo@21
|
183 system call was invented at Berkeley. It completely omits copying the
|
|
meillo@21
|
184 image. If the image gets replaced right afterwards then unnecessary
|
|
meillo@21
|
185 work is omited. On old systems this results in large speed ups.
|
|
meillo@21
|
186 MH uses
|
|
meillo@21
|
187 .Fu vfork()
|
|
meillo@21
|
188 whenever possible.
|
|
meillo@21
|
189 .P
|
|
meillo@21
|
190 Memory management units that support copy-on-write semantics make
|
|
meillo@21
|
191 .Fu fork()
|
|
meillo@21
|
192 almost as fast as
|
|
meillo@21
|
193 .Fu vfork()
|
|
meillo@21
|
194 in the cases when they can be exchanged.
|
|
meillo@21
|
195 With
|
|
meillo@21
|
196 .Fu vfork()
|
|
meillo@21
|
197 being more errorprone and hardly faster, it's preferable to simply
|
|
meillo@21
|
198 use
|
|
meillo@21
|
199 .Fu fork()
|
|
meillo@21
|
200 instead.
|
|
meillo@21
|
201 .P
|
|
meillo@21
|
202 Related to the costs of
|
|
meillo@21
|
203 .Fu fork()
|
|
meillo@21
|
204 is the probability of its success.
|
|
meillo@21
|
205 Today on modern systems, the system call will succeed almost always.
|
|
meillo@21
|
206 In the 80s on heavy loaded systems, as they were common at
|
|
meillo@21
|
207 universities, this had been different. Thus, many of the
|
|
meillo@21
|
208 .Fu fork()
|
|
meillo@21
|
209 calls were wrapped into loops to retry to fork several times in
|
|
meillo@21
|
210 short intervals, in case of previous failure.
|
|
meillo@21
|
211 In mmh, the program aborts at once if the fork failed.
|
|
meillo@21
|
212 The user can reexecute the command then. This is expected to be a
|
|
meillo@21
|
213 very rare case on modern systems, especially personal ones, which are
|
|
meillo@21
|
214 common today.
|
|
meillo@21
|
215
|
|
meillo@12
|
216
|
|
meillo@14
|
217 .H1 "Draft and Trash Folders
|
|
meillo@16
|
218 .U2 "Draft Folder
|
|
meillo@14
|
219 .P
|
|
meillo@18
|
220 Historically, MH provided exactly one draft message, named
|
|
meillo@18
|
221 .Fn draft
|
|
meillo@18
|
222 and
|
|
meillo@14
|
223 being located in the MH directory. When starting to compose another message
|
|
meillo@14
|
224 before the former one was sent, the user had been questioned wether to use,
|
|
meillo@14
|
225 refile or replace the old draft. Working on multiple drafts at the same time
|
|
meillo@14
|
226 was impossible. One could only work on them in alteration by refiling the
|
|
meillo@14
|
227 previous one to some directory and fetching some other one for reediting.
|
|
meillo@14
|
228 This manual draft management needed to be done each time the user wanted
|
|
meillo@14
|
229 to switch between editing one draft to editing another.
|
|
meillo@14
|
230 .P
|
|
meillo@14
|
231 To allow true parallel editing of drafts, in a straight forward way, the
|
|
meillo@14
|
232 draft folder facility exists. It had been introduced already in July 1984
|
|
meillo@14
|
233 by Marshall T. Rose. The facility was deactivated by default.
|
|
meillo@14
|
234 Even in nmh, the draft folder facility remained deactivated by default.
|
|
meillo@18
|
235 At least, Richard Coleman added the man page
|
|
meillo@18
|
236 .Mp mh-draft(5)
|
|
meillo@18
|
237 to document
|
|
meillo@14
|
238 the feature well.
|
|
meillo@14
|
239 .P
|
|
meillo@14
|
240 The only advantage of not using the draft folder facility is the static
|
|
meillo@14
|
241 name of the draft file. This could be an issue for MH frontends like mh-e.
|
|
meillo@14
|
242 But as they likely want to provide working on multiple drafts in parallel,
|
|
meillo@14
|
243 the issue is only concerning compatibility. The aim of nmh to stay compatible
|
|
meillo@14
|
244 prevented the default activation of the draft folder facility.
|
|
meillo@14
|
245 .P
|
|
meillo@14
|
246 On the other hand, a draft folder is the much more natural concept than
|
|
meillo@14
|
247 a draft message. MH's mail storage consists of folders and messages,
|
|
meillo@14
|
248 the messages named with ascending numbers. A draft message breaks with this
|
|
meillo@18
|
249 concept by introducing a message in a file named
|
|
meillo@18
|
250 .Fn draft .
|
|
meillo@18
|
251 This draft
|
|
meillo@14
|
252 message is special. It can not be simply listed with the available tools,
|
|
meillo@17
|
253 but instead requires special switches. I.e. corner-cases were
|
|
meillo@14
|
254 introduced. A draft folder, in contrast, does not introduce such
|
|
meillo@14
|
255 corner-cases. The available tools can operate on the messages within that
|
|
meillo@14
|
256 folder like on any messages within any mail folders. The only difference
|
|
meillo@18
|
257 is the fact that the default folder for
|
|
meillo@18
|
258 .Pn send
|
|
meillo@18
|
259 is the draft folder,
|
|
meillo@14
|
260 instead of the current folder, like for all other tools.
|
|
meillo@14
|
261 .P
|
|
meillo@14
|
262 The trivial part of the change was activating the draft folder facility
|
|
meillo@14
|
263 by default and setting a default name for this folder. Obviously, I chose
|
|
meillo@18
|
264 the name
|
|
meillo@18
|
265 .Fn +drafts .
|
|
meillo@18
|
266 This made the
|
|
meillo@18
|
267 .Sw \-draftfolder
|
|
meillo@18
|
268 and
|
|
meillo@18
|
269 .Sw \-draftmessage
|
|
meillo@18
|
270 switches useless, and I could remove them.
|
|
meillo@14
|
271 The more difficult but also the part that showed the real improvement,
|
|
meillo@18
|
272 was updating the tools to the new concept.
|
|
meillo@18
|
273 .Sw \-draft
|
|
meillo@18
|
274 switches could
|
|
meillo@14
|
275 be dropped, as operating on a draft message became indistinguishable to
|
|
meillo@18
|
276 operating on any other message for the tools.
|
|
meillo@18
|
277 .Pn comp
|
|
meillo@18
|
278 still has its
|
|
meillo@18
|
279 .Sw \-use
|
|
meillo@18
|
280 switch for switching between its two modes: (1) Compose a new
|
|
meillo@14
|
281 draft, possibly by taking some existing message as a form. (2) Modify
|
|
meillo@18
|
282 an existing draft. In either case, the behavior of
|
|
meillo@18
|
283 .Pn comp is
|
|
meillo@14
|
284 deterministic. There is no more need to query the user. I consider this
|
|
meillo@18
|
285 a major improvement. By making
|
|
meillo@18
|
286 .Pn send
|
|
meillo@18
|
287 simply operate on the current
|
|
meillo@17
|
288 message in the draft folder by default, with message and folder both
|
|
meillo@14
|
289 overridable by specifying them on the command line, it is now possible
|
|
meillo@17
|
290 to send a draft anywhere within the storage by simply specifying its folder
|
|
meillo@17
|
291 and name.
|
|
meillo@14
|
292 .P
|
|
meillo@14
|
293 All theses changes converted special cases to regular cases, thus
|
|
meillo@14
|
294 simplifying the tools and increasing the flexibility.
|
|
meillo@14
|
295
|
|
meillo@16
|
296 .U2 "Trash Folder
|
|
meillo@16
|
297 .P
|
|
meillo@16
|
298 Similar to the situation for drafts is the situation for removed messages.
|
|
meillo@16
|
299 Historically, a message was deleted by renaming. A specific
|
|
meillo@18
|
300 \fIbackup prefix\fP, often comma (\c
|
|
meillo@18
|
301 .Fn , )
|
|
meillo@18
|
302 or hash (\c
|
|
meillo@18
|
303 .Fn # ),
|
|
meillo@16
|
304 being prepended to the file name. Thus, MH wouldn't recognize the file
|
|
meillo@16
|
305 as a message anymore, as only files whose name consists of digits only
|
|
meillo@16
|
306 are treated as messages. The removed messages remained as files in the
|
|
meillo@16
|
307 same directory and needed some maintenance job to truly delete them after
|
|
meillo@16
|
308 some grace time. Usually, by running a command similar to
|
|
meillo@16
|
309 .DS
|
|
meillo@16
|
310 find /home/user/Mail \-ctime +7 \-name ',*' | xargs rm
|
|
meillo@16
|
311 .DE
|
|
meillo@16
|
312 in a cron job. Within the grace time interval
|
|
meillo@16
|
313 the original message could be restored by stripping the
|
|
meillo@16
|
314 the backup prefix from the file name. If however, the last message of
|
|
meillo@18
|
315 a folder is been removed \(en say message
|
|
meillo@18
|
316 .Fn 6
|
|
meillo@18
|
317 becomes file
|
|
meillo@18
|
318 .Fn ,6
|
|
meillo@18
|
319 \(en and a new message enters the same folder, thus the same
|
|
meillo@18
|
320 numbered being given again \(en in our case
|
|
meillo@18
|
321 .Fn 6
|
|
meillo@18
|
322 \(en, if that one
|
|
meillo@17
|
323 is removed too, then the backup of the former message gets overwritten.
|
|
meillo@16
|
324 Thus, the ability to restore removed messages does not only depend on
|
|
meillo@16
|
325 the ``sweeping cron job'' but also on the removing of further messages.
|
|
meillo@16
|
326 This is undesireable, because the real mechanism is hidden from the user
|
|
meillo@16
|
327 and the concequences of further removals are not always obvious.
|
|
meillo@16
|
328 Further more, the backup files are scattered within the whole mail
|
|
meillo@16
|
329 storage, instead of being collected at one place.
|
|
meillo@16
|
330 .P
|
|
meillo@18
|
331 To improve the situation, the profile entry
|
|
meillo@18
|
332 .Pe rmmproc
|
|
meillo@18
|
333 (previously named
|
|
meillo@18
|
334 .Pe Delete-Prog )
|
|
meillo@18
|
335 was introduced, very early.
|
|
meillo@16
|
336 It could be set to any command, which would care for the mail removal
|
|
meillo@16
|
337 instead of taking the default action, described above.
|
|
meillo@16
|
338 Refiling the to-be-removed files to some wastebin folder was a common
|
|
meillo@18
|
339 example. Nmh's man page
|
|
meillo@18
|
340 .Mp rmm(1)
|
|
meillo@18
|
341 proposes
|
|
meillo@18
|
342 .Cl "refile +d
|
|
meillo@18
|
343 to move messages to the wastebin and
|
|
meillo@18
|
344 .Cl "rm `mhpath +d all`
|
|
meillo@16
|
345 the empty the wastebin.
|
|
meillo@16
|
346 Managing the message removal this way is a sane approach. It keeps
|
|
meillo@16
|
347 the removed messages in one place, makes it easy to remove the backup
|
|
meillo@16
|
348 files, and, most important, enables the user to use the tools of MH
|
|
meillo@18
|
349 itself to operate on the removed messages. One can
|
|
meillo@18
|
350 .Pn scan
|
|
meillo@18
|
351 them,
|
|
meillo@18
|
352 .Pn show
|
|
meillo@18
|
353 them, and restore them with
|
|
meillo@18
|
354 .Pn refile .
|
|
meillo@18
|
355 There's no more
|
|
meillo@18
|
356 need to use
|
|
meillo@18
|
357 .Pn mhpath
|
|
meillo@18
|
358 to switch over from MH tools to Unix tools \(en MH can do it all itself.
|
|
meillo@16
|
359 .P
|
|
meillo@18
|
360 This apporach matches perfect with the concepts of MH, thus making
|
|
meillo@16
|
361 it powerful. Hence, I made it the default. And even more, I also
|
|
meillo@16
|
362 removed the old backup prefix approach, as it is clearly less powerful.
|
|
meillo@16
|
363 Keeping unused alternative in the code is a bad choice as they likely
|
|
meillo@16
|
364 gather bugs, by not being constantly tested. Also, the increased code
|
|
meillo@16
|
365 size and more conditions crease the maintenance costs. By strictly
|
|
meillo@16
|
366 converting to the trash folder approach, I simplified the code base.
|
|
meillo@18
|
367 .Pn rmm
|
|
meillo@18
|
368 calls
|
|
meillo@18
|
369 .Pn refile
|
|
meillo@18
|
370 internally to move the to-be-removed
|
|
meillo@18
|
371 message to the trash folder (\c
|
|
meillo@18
|
372 .Fn +trash
|
|
meillo@18
|
373 by default). Messages
|
|
meillo@16
|
374 there can be operated on like on any other message in the storage.
|
|
meillo@18
|
375 The sweep clean, one can use
|
|
meillo@18
|
376 .Cl "rmm \-unlink +trash a" ,
|
|
meillo@18
|
377 where the
|
|
meillo@18
|
378 .Sw \-unlink
|
|
meillo@18
|
379 switch causes the files to be truly unliked instead
|
|
meillo@16
|
380 of moved to the trash folder.
|
|
meillo@16
|
381
|
|
meillo@0
|
382
|
|
meillo@17
|
383 .H1 "MH Directory Split
|
|
meillo@0
|
384 .P
|
|
meillo@19
|
385 In MH and nmh, a personal setup had consisted of two parts:
|
|
meillo@19
|
386 The MH profile, named
|
|
meillo@19
|
387 .Fn \&.mh_profile
|
|
meillo@19
|
388 and being located directly in the user's home directory.
|
|
meillo@19
|
389 And the MH directory, where all his mail messages and also his personal
|
|
meillo@19
|
390 forms, scan formats, other configuration files are stored. The location
|
|
meillo@19
|
391 of this directory could be user-chosen. The default was to name it
|
|
meillo@19
|
392 .Fn Mail
|
|
meillo@19
|
393 and have it directly in the home directory.
|
|
meillo@19
|
394 .P
|
|
meillo@19
|
395 I've never liked the data storage and the configuration to be intermixed.
|
|
meillo@19
|
396 They are different kinds of data. One part, are the messages,
|
|
meillo@19
|
397 which are the data to operate on. The other part, are the personal
|
|
meillo@19
|
398 configuration files, which are able to change the behavior of the operations.
|
|
meillo@19
|
399 The actual operations are defined in the profile, however.
|
|
meillo@19
|
400 .P
|
|
meillo@19
|
401 When storing data, one should try to group data by its type.
|
|
meillo@19
|
402 There's sense in the Unix file system hierarchy, where configuration
|
|
meillo@19
|
403 file are stored separate (\c
|
|
meillo@19
|
404 .Fn /etc )
|
|
meillo@19
|
405 to the programs (\c
|
|
meillo@19
|
406 .Fn /bin
|
|
meillo@19
|
407 and
|
|
meillo@19
|
408 .Fn /usr/bin )
|
|
meillo@19
|
409 to their sources (\c
|
|
meillo@19
|
410 .Fn /usr/src ).
|
|
meillo@19
|
411 Such separation eases the backup management, for instance.
|
|
meillo@19
|
412 .P
|
|
meillo@19
|
413 In mmh, I've reorganized the file locations.
|
|
meillo@19
|
414 Still there are two places:
|
|
meillo@19
|
415 There's the mail storage directory, which, like in MH, contains all the
|
|
meillo@19
|
416 messages, but, unlike in MH, nothing else.
|
|
meillo@19
|
417 Its location still is user-chosen, with the default name
|
|
meillo@19
|
418 .Fn Mail ,
|
|
meillo@19
|
419 in the user's home directory. This is much similar to the case in nmh.
|
|
meillo@19
|
420 The configuration files, however, are grouped together in the new directory
|
|
meillo@19
|
421 .Fn \&.mmh
|
|
meillo@19
|
422 in the user's home directory.
|
|
meillo@19
|
423 The user's profile now is a file, named
|
|
meillo@19
|
424 .Fn profile ,
|
|
meillo@19
|
425 in this mmh directory.
|
|
meillo@19
|
426 Consistently, the context file and all the personal forms, scan formats,
|
|
meillo@19
|
427 and the like, are also there.
|
|
meillo@19
|
428 .P
|
|
meillo@19
|
429 The naming changed with the relocation.
|
|
meillo@19
|
430 The directory where everything, except the profile, had been stored (\c
|
|
meillo@19
|
431 .Fn $HOME/Mail ),
|
|
meillo@19
|
432 used to be called \fIMH directory\fP. Now, this directory is called the
|
|
meillo@19
|
433 user's \fImail storage\fP. The name \fImmh directory\fP is now given to
|
|
meillo@19
|
434 the new directory
|
|
meillo@19
|
435 (\c
|
|
meillo@19
|
436 .Fn $HOME/.mmh ),
|
|
meillo@19
|
437 containing all the personal configuration files.
|
|
meillo@19
|
438 .P
|
|
meillo@19
|
439 The separation of the files by type of content is logical and convenient.
|
|
meillo@19
|
440 There are no functional differences as any possible setup known to me
|
|
meillo@19
|
441 can be implemented with both approaches, although likely a bit easier
|
|
meillo@19
|
442 with the new approach. The main goal of the change had been to provide
|
|
meillo@19
|
443 sensible storage locations for any type of personal mmh file.
|
|
meillo@19
|
444 .P
|
|
meillo@19
|
445 In order for one user to have multiple MH setups, he can use the
|
|
meillo@19
|
446 environment variable
|
|
meillo@19
|
447 .Ev MH
|
|
meillo@19
|
448 the point to a different profile file.
|
|
meillo@19
|
449 The MH directory (mail storage plus personal configuration files) is
|
|
meillo@19
|
450 defined by the
|
|
meillo@19
|
451 .Pe Path
|
|
meillo@19
|
452 profile entry.
|
|
meillo@19
|
453 The context file could be defined by the
|
|
meillo@19
|
454 .Pe context
|
|
meillo@19
|
455 profile entry or by the
|
|
meillo@19
|
456 .Ev MHCONTEXT
|
|
meillo@19
|
457 environment variable.
|
|
meillo@19
|
458 The latter is useful to have a distinct context (e.g. current folders)
|
|
meillo@19
|
459 in each terminal window, for instance.
|
|
meillo@19
|
460 In mmh, there are three environment variables now.
|
|
meillo@19
|
461 .Ev MMH
|
|
meillo@19
|
462 may be used to change the location of the mmh directory.
|
|
meillo@19
|
463 .Ev MMHP
|
|
meillo@19
|
464 and
|
|
meillo@19
|
465 .Ev MMHC
|
|
meillo@19
|
466 change the profile and context files, respectively.
|
|
meillo@19
|
467 Besides providing a more consistent feel (which simply is the result
|
|
meillo@19
|
468 of being designed anew), the set of personal configuration files can
|
|
meillo@19
|
469 be chosen independently from the profile (including mail storage location)
|
|
meillo@19
|
470 and context, now. Being it relevant for practical use or not, it
|
|
meillo@19
|
471 de-facto is an improvement. However, the main achievement is the
|
|
meillo@19
|
472 split between mail storage and personal configuration files.
|
|
meillo@17
|
473
|
|
meillo@0
|
474
|
|
meillo@0
|
475 .H1 "Path Notations
|
|
meillo@0
|
476 .P
|
|
meillo@0
|
477 foo
|
|
meillo@0
|
478
|
|
meillo@0
|
479 .H1 "Attachments
|
|
meillo@0
|
480 .P
|
|
meillo@0
|
481 foo
|
|
meillo@0
|
482
|
|
meillo@20
|
483 .H1 "mhshow to show Transition
|
|
meillo@20
|
484 .P
|
|
meillo@20
|
485 Since the very beginning, already in the first concept paper,
|
|
meillo@20
|
486 .Pn show
|
|
meillo@20
|
487 had been MH's mail display program.
|
|
meillo@20
|
488 .Pn show
|
|
meillo@20
|
489 found out which pathnames the relevant messages had and invoked
|
|
meillo@20
|
490 .Pn mhl
|
|
meillo@20
|
491 then to let it render the content.
|
|
meillo@20
|
492 With the advent of MIME, this approach wasn't sufficient anymore.
|
|
meillo@20
|
493 MIME messages can consist of multiple parts, some of which aren't
|
|
meillo@20
|
494 directly displayable, and text content can be encoded in
|
|
meillo@20
|
495 foreign charsets.
|
|
meillo@20
|
496 .Pn show 's
|
|
meillo@20
|
497 simple approach and
|
|
meillo@20
|
498 .Pn mhl 's
|
|
meillo@20
|
499 limited display facilities couldn't cope with the task any longer.
|
|
meillo@20
|
500 Instead of extending these tools, new ones were written from scratch
|
|
meillo@20
|
501 and then added to the MH toolchest. Doing so is encouraged by the
|
|
meillo@20
|
502 toolchest approach. The new tools could be added without interfearing
|
|
meillo@20
|
503 with the existing ones. This is great. It allowed MH to be the
|
|
meillo@20
|
504 first MUA to implement MIME.
|
|
meillo@20
|
505 .P
|
|
meillo@20
|
506 The new MIME features were added in form of the single program
|
|
meillo@20
|
507 .Pn mhn .
|
|
meillo@20
|
508 The command
|
|
meillo@20
|
509 .DS
|
|
meillo@20
|
510 mhn \-show 42
|
|
meillo@20
|
511 .DE
|
|
meillo@20
|
512 would show the MIME message numbered 42.
|
|
meillo@20
|
513 With the 1.0 release of nmh in February 1999, Richard Coleman finished
|
|
meillo@20
|
514 the split of
|
|
meillo@20
|
515 .Pn mhn
|
|
meillo@20
|
516 into a set of specialized programs, which together covered the
|
|
meillo@20
|
517 aspects of MIME. One of these resulting tools was
|
|
meillo@20
|
518 .Pn mhshow .
|
|
meillo@20
|
519
|
|
meillo@20
|
520
|
|
meillo@0
|
521 .H1 "Blind Carbon Copies
|
|
meillo@0
|
522 .P
|
|
meillo@0
|
523 foo
|
|
meillo@0
|
524
|
|
meillo@0
|
525 .H1 "Good Defaults
|
|
meillo@0
|
526 .P
|
|
meillo@0
|
527 foo
|
|
meillo@0
|
528
|
|
meillo@0
|
529 .H1 "Modularization
|
|
meillo@0
|
530 .P
|
|
meillo@0
|
531 foo
|
|
meillo@0
|
532
|
|
meillo@0
|
533 .H1 "Code style
|
|
meillo@0
|
534 .P
|
|
meillo@0
|
535 foo
|
