Mercurial > docs > master
comparison ch03.roff @ 22:99409e4546d2
Wrote about the removal of tools.
author | markus schnalke <meillo@marmaro.de> |
---|---|
date | Mon, 07 May 2012 17:27:57 +0200 |
parents | bb8a8be49024 |
children | 1e4afeb34da7 |
comparison
equal
deleted
inserted
replaced
21:bb8a8be49024 | 22:99409e4546d2 |
---|---|
210 short intervals, in case of previous failure. | 210 short intervals, in case of previous failure. |
211 In mmh, the program aborts at once if the fork failed. | 211 In mmh, the program aborts at once if the fork failed. |
212 The user can reexecute the command then. This is expected to be a | 212 The user can reexecute the command then. This is expected to be a |
213 very rare case on modern systems, especially personal ones, which are | 213 very rare case on modern systems, especially personal ones, which are |
214 common today. | 214 common today. |
215 | |
216 | |
217 .H1 "Removal of Tools | |
218 .P | |
219 MH had been considered an all-in-one system for mail handling. | |
220 The community around nmh has a similar understanding. | |
221 In fundamental difference, I believe that mmh should be a MUA but | |
222 nothing more. I believe that all-in-one mail systems are not the way | |
223 to go. There are excellent specialized MTAs, like Postfix; | |
224 there are specialized MDAs, like Procmail; there are specialized | |
225 MRAs, like Fetchmail. I believe it's best to use them instead of | |
226 providing the same function ourself. Doing something well requires to | |
227 focus on this particular aspect or a small set of aspects. The more | |
228 it is possible to focus, the better the result in this particular | |
229 area will be. The limiting resource in Free Software community development | |
230 usually is human power. If the low development power is even parted | |
231 into multiple development areas, it will hardly be possible to | |
232 compete with the specialists in the various fields. This is even | |
233 increased, given the small community \(en developers and users \(en | |
234 that MH-based mail systems have. In consequence, I believe that the | |
235 available resources should be concentrated at the point where MH is | |
236 most unique. This is clearly the MUA part. | |
237 .P | |
238 Several of nmh's tools were removed from mmh because they didn't | |
239 match the main focus of adding to the MUA's task. | |
240 .P | |
241 .Pn conflict | |
242 was removed because it is a mail system maintenance tool. | |
243 Besides, it also checks the | |
244 .Fn /etc/passwd | |
245 and | |
246 .Fn /etc/group | |
247 files. | |
248 The tool might be useful, but it should not be shipped with mmh. | |
249 .P | |
250 .Pn rcvtty | |
251 was removed because its usecase of writing to the user's terminal | |
252 on receival of mail is hardly wanted today. If users like to be | |
253 informed of new mail, then using the shell's | |
254 .Ev MAILPATH | |
255 variable or different (graphical) notifications are likely more | |
256 appealing. Writing directly to other terminals is hardly ever wanted | |
257 today. If though one wants to have it this way, the standard tool | |
258 .Pn write | |
259 can be used in a way similar to: | |
260 .DS | |
261 scan -file - | write `id -un` | |
262 .DE | |
263 .P | |
264 When the new attachment system was introduced, | |
265 .Pn viamail | |
266 was removed because then | |
267 .Pn forw | |
268 could cover the task itself. | |
269 The wrapper program | |
270 .Pn sendfiles | |
271 was rewritten as a shell script to use | |
272 .Pn forw . | |
273 .P | |
274 .Pn msgchk | |
275 was removed as it became hardly useful when POP support was removed. | |
276 It is questionable if | |
277 .Pn msgchk | |
278 provides more information than: | |
279 .DS | |
280 ls -l /var/mail/meillo | |
281 .DE | |
282 It does separate between old and new mail, but that's not very | |
283 useful and can be found out with | |
284 .Pn stat (1) | |
285 too. A very small shell script could care for the form of output. | |
286 As mmh's inc only incorporates mail from the user's local maildrop | |
287 and thus no long data transfers are involved, | |
288 there's no need to check for new mail before incorporating it. | |
289 .P | |
290 .Pn msh | |
291 was removed because the tool was in conflict with the original | |
292 philosophy of MH. It provided an interactive shell to access the | |
293 features of MH. One major feature of MH is being a toolchest. | |
294 .Pn msh | |
295 wouldn't be just another shell, taylored to the needs of mail | |
296 handling, but one large program to have the MH tools built in. | |
297 It's main use was for accessing Bulletin Boards, which have seized to | |
298 be popular. Removing | |
299 .Pn msh , | |
300 together with the truly obsolete programs | |
301 .Pn vmh | |
302 and | |
303 .Pn wmh , | |
304 saved more than 7\|000 lines of C code \(en a major achievement. | |
215 | 305 |
216 | 306 |
217 .H1 "Draft and Trash Folders | 307 .H1 "Draft and Trash Folders |
218 .U2 "Draft Folder | 308 .U2 "Draft Folder |
219 .P | 309 .P |