1.1 --- a/bib	Tue Jun 05 22:23:51 2012 +0200
     1.2 +++ b/bib	Tue Jun 05 22:24:10 2012 +0200
     1.3 @@ -239,3 +239,9 @@
     1.4  %T Commands and Utilities (XCU), Issue 4
     1.5  %O \s-2ISBN\s0: 1-872630-48-0
     1.6  
     1.7 +%L Wolter04
     1.8 +%A Jan Wolter
     1.9 +%T DBM Hash Libraries
    1.10 +%B Unix Incompatibility Notes
    1.11 +%D 2000\(en2004
    1.12 +%O \f(CW\s-1http://www.unixpapa.com/incnote/dbm.html\s0

     2.1 --- a/ch03.roff	Tue Jun 05 22:23:51 2012 +0200
     2.2 +++ b/ch03.roff	Tue Jun 05 22:24:10 2012 +0200
     2.3 @@ -303,7 +303,9 @@
     2.4  .Pn slocal .
     2.5  .Pn slocal
     2.6  is an MDA and thus not directly MUA-related.
     2.7 -Conceptionally, it should be removed.
     2.8 +It should be removed, because including it is a violation
     2.9 +of the idea that mmh is a MUA only.
    2.10 +It should become a separate project.
    2.11  But
    2.12  .Pn slocal
    2.13  provides rule-based processing of messages, like filing them into
    2.14 @@ -332,9 +334,14 @@
    2.15  That's conceptionally the best solution.
    2.16  Yet,
    2.17  .Pn slocal
    2.18 -is not removed,
    2.19 -but as its existence does not affect the rest of mmh,
    2.20 -it can be removed at any time.
    2.21 +was not removed.
    2.22 +I feel unsure with the removal.
    2.23 +Hence, the decision over
    2.24 +.Pn slocal
    2.25 +is deferred.
    2.26 +This does not hurt because
    2.27 +.Pn slocal
    2.28 +is completely unrelated to the rest of mmh.
    2.29  
    2.30  
    2.31  .H2 "\fLshow\fP and \fPmhshow\fP
    2.32 @@ -358,10 +365,8 @@
    2.33  Instead of extending these tools, additional tools were written from scratch
    2.34  and then added to the MH tool chest. Doing so is encouraged by the
    2.35  tool chest approach. The new tools could be added without interfering
    2.36 -with the existing ones. This is an advantage. The ease of adding new tools
    2.37 -made MH the first MUA to implement MIME.
    2.38 -.\" XXX ref
    2.39 -.P
    2.40 +with the existing ones.
    2.41 +Modular design is a great advantage for extending a system.
    2.42  First, the new MIME features were added in form of the single program
    2.43  .Pn mhn .
    2.44  The command
    2.45 @@ -495,11 +500,20 @@
    2.46  The backup prefix is the string that was prepended to message
    2.47  filenames to tag them as deleted.
    2.48  By default it had been the comma character `\f(CW,\fP'.
    2.49 -There was a configure option to change the default to the hash symbol
    2.50 -`\f(CW#\fP':
    2.51 -.CW --with-hash-backup .
    2.52 -The implication of the hash symbol is that it introduces a comment
    2.53 -in the Unix shell.
    2.54 +In July 2000, Kimmo Suominen introduced
    2.55 +the configure option
    2.56 +.Sw --with-hash-backup
    2.57 +to change the default to the hash symbol `\f(CW#\fP'.
    2.58 +The choice was probably personal preference, because first, the
    2.59 +option was named
    2.60 +.Sw --with-backup-prefix.
    2.61 +and had the prefix symbol as argument.
    2.62 +Because giving the hash symbol as argument caused to many problems
    2.63 +for configure,
    2.64 +the option was limited to use the hash symbol as the default prefix.
    2.65 +This makes me believe, that the choice for the hash was personal preference.
    2.66 +Being it related or not, words that start with the hash symbol
    2.67 +introduce a comment in the Unix shell.
    2.68  Thus, the command line
    2.69  .Cl "rm #13 #15
    2.70  calls
    2.71 @@ -509,8 +523,9 @@
    2.72  To delete the backup files,
    2.73  .Cl "rm ./#13 ./#15"
    2.74  needs to be used.
    2.75 -.\" XXX check historical background
    2.76 -Besides this effect, the choice was personal preference.
    2.77 +Using the hash as backup prefix can be seen as a precaution agains
    2.78 +data loss.
    2.79 +.P
    2.80  I removed the configure option but added the profile entry
    2.81  .Pe backup-prefix ,
    2.82  which allows to specify an arbitrary string as backup prefix.
    2.83 @@ -519,8 +534,10 @@
    2.84  This change did not remove the choice but moved it to a location where
    2.85  it suited better.
    2.86  .P
    2.87 -Eventually, however, the new trash folder obsoleted the concept of the
    2.88 -backup prefix completely.
    2.89 +Eventually, however, the new trash folder concept
    2.90 +.Cf "Sec. XXX
    2.91 +obsoleted the concept of the backup prefix completely.
    2.92 +.Ci 8edc5aaf86f9f77124664f6801bc6c6cdf258173
    2.93  (Well, there still are corner-cases to remove until the backup
    2.94  prefix can be layed to rest, eventually.)
    2.95  .\" FIXME: Do this work in the code!
    2.96 @@ -626,17 +643,7 @@
    2.97  .U3 "ndbm
    2.98  .P
    2.99  .Pn slocal
   2.100 -is an MDA included in mmh.
   2.101 -This is a violation of the idea that mmh is a MUA only.
   2.102 -.Pn slocal
   2.103 -should become a separate project.
   2.104 -Nonetheless, ouf of convenience and due to lack of convincement,
   2.105 -yet it remains being part of mmh.
   2.106 -This is likely to change in the future.
   2.107 -Already,
   2.108 -.Pn slocal
   2.109 -was stripped down.
   2.110 -It used to depend on
   2.111 +used to depend on
   2.112  .I ndbm ,
   2.113  a database library.
   2.114  The database is used to store the `\fLMessage-ID\fP's of all
   2.115 @@ -649,24 +656,25 @@
   2.116  switch.)
   2.117  .P
   2.118  A variety of version of the database library exist.
   2.119 +.[
   2.120 +wolter unix incompat notes dbm
   2.121 +.]
   2.122  Complicated autoconf code was needed to detect them correctly.
   2.123  Further more, the configure switches
   2.124  .Sw --with-ndbm=ARG
   2.125  and
   2.126  .Sw --with-ndbmheader=ARG
   2.127  were added to help with difficult setups that would
   2.128 -not be detected automatically.
   2.129 +not be detected automatically or correctly.
   2.130  .P
   2.131  By removing the suppress duplicates feature of
   2.132  .Pn slocal ,
   2.133 -.Ci ecd6d6a20cb7a1507e3a20d6c4cb3a1cf14c6bbf
   2.134  the dependency on
   2.135  .I ndbm
   2.136 -was removed and 120 lines of complex autoconf could be saved.
   2.137 +vanished and 120 lines of complex autoconf code could be saved.
   2.138  .Ci ecd6d6a20cb7a1507e3a20d6c4cb3a1cf14c6bbf
   2.139 -The change removed funtionality too, but the value it would have added
   2.140 -is minor to the weight loss by dropping the dependency and 
   2.141 -the complex autoconf code.
   2.142 +The change removed funtionality too, but that is minor to the
   2.143 +improvement by dropping the dependency and the complex autoconf code.
   2.144  
   2.145  .U3 "mh-e Support
   2.146  .P