1.1 --- a/discussion.roff	Wed Jul 11 00:00:34 2012 +0200
     1.2 +++ b/discussion.roff	Wed Jul 11 09:24:47 2012 +0200
     1.3 @@ -274,7 +274,7 @@
     1.4  .H2 "Non-MUA Tools
     1.5  .P
     1.6  One goal of mmh is to remove the tools that are not part of the MUA's task.
     1.7 -Further more, any tools that do not significantly improve the MUA's job
     1.8 +Furthermore, any tools that do not significantly improve the MUA's job
     1.9  should be removed.
    1.10  Loosely related and rarely used tools distract from the lean appearance.
    1.11  They require maintenance work without adding much to the core task.
    1.12 @@ -823,7 +823,7 @@
    1.13  wolter unix incompat notes dbm
    1.14  .]
    1.15  Complicated autoconf code was needed to detect them correctly.
    1.16 -Further more, the configure switches
    1.17 +Furthermore, the configure switches
    1.18  .Sw --with-ndbm=ARG
    1.19  and
    1.20  .Sw --with-ndbmheader=ARG
    1.21 @@ -898,7 +898,7 @@
    1.22  .I fakeusername
    1.23  mapping, based on the password file's GECOS field.
    1.24  The man page
    1.25 -.Mp mh-tailor(5)
    1.26 +.Mp mh-tailor (5)
    1.27  described the use case as being the following:
    1.28  .QS
    1.29  This is useful if you want the messages you send to always
    1.30 @@ -913,7 +913,7 @@
    1.31  the best location to do such global rewrites is there.
    1.32  Besides, the MTA is conceptionally the right location because it
    1.33  does the reverse mapping for incoming mail (aliasing), too.
    1.34 -Further more, masquerading set up there is readily available for all
    1.35 +Furthermore, masquerading set up there is readily available for all
    1.36  mail software on the system.
    1.37  Hence, mmailid masquerading was removed.
    1.38  .Ci 0836c8000ccb34b59410ef1c15b1b7feac70ce5f
    1.39 @@ -1880,7 +1880,7 @@
    1.40  The mind model of email attachments is unrelated to MIME.
    1.41  Although the MIME RFCs (2045 through 2049) define the technical
    1.42  requirements for having attachments, they do not mention the word
    1.43 -``attachment''.
    1.44 +attachment.
    1.45  Instead of attachments, MIME talks about ``multi-part message bodies''
    1.46  [RFC\|2045], a more general concept.
    1.47  Multi-part messages are messages
    1.48 @@ -2428,7 +2428,7 @@
    1.49  Both scripts were written for nmh, hence they needed to be adjust
    1.50  according to the differences between nmh and mmh.
    1.51  For instance, they use the backup prefix no longer.
    1.52 -Further more, compatibility support for old PGP features was dropped.
    1.53 +Furthermore, compatibility support for old PGP features was dropped.
    1.54  .P
    1.55  The integrated message signing and encrypting support is one of the
    1.56  most recent features in mmh.
    1.57 @@ -2608,7 +2608,7 @@
    1.58  If this new message would be removed as well,
    1.59  then the backup of the former message is overwritten.
    1.60  Hence, the ability to restore removed messages did not only depend on
    1.61 -the ``sweeping cron job'' but also on the removing of further messages.
    1.62 +the sweeping cron job but also on the removing of further messages.
    1.63  It is undesirable to have such obscure and complex mechanisms.
    1.64  The user should be given a small set of clear assertions, such as
    1.65  ``Removed files are restorable within a seven-day grace time.''
    1.66 @@ -2619,7 +2619,7 @@
    1.67  In practice, the real mechanism is unclear to the user.
    1.68  The consequences of further removals are not obvious.
    1.69  .P
    1.70 -Further more, the backup files are scattered within the whole mail storage.
    1.71 +Furthermore, the backup files are scattered within the whole mail storage.
    1.72  This complicates managing them.
    1.73  It is possible with the help of
    1.74  .Pn find ,
    1.75 @@ -2928,7 +2928,11 @@
    1.76  to
    1.77  .Fu is_native_charset() .
    1.78  .Ci 8d77b48284c58c135a6b2787e721597346ab056d
    1.79 -The same change fixed a violation of ``Be accurate'' as well.
    1.80 +The same change fixed a violation of ``Be accurate''
    1.81 +.[ [
    1.82 +kernighan pike practice of programming
    1.83 +.], p. 4]
    1.84 +as well.
    1.85  The code did not match the expectation the function suggested,
    1.86  as it, for whatever reason, only compared the first ten characters
    1.87  of the charset name.
    1.88 @@ -2995,6 +2999,9 @@
    1.89  .P
    1.90  At the end of their chapter on style,
    1.91  Kernighan and Pike ask: ``But why worry about style?''
    1.92 +.[ [
    1.93 +kernighan pike practice of programming
    1.94 +.], p. 28]
    1.95  Following are two examples of structural rework that show
    1.96  why style is important in the first place.
    1.97  
    1.98 @@ -3345,7 +3352,7 @@
    1.99  MH tools read the profile right after starting up,
   1.100  as it contains the location of the user's mail storage
   1.101  and similar settings that influence the whole setup.
   1.102 -Further more, the profile contains the default switches for the tools,
   1.103 +Furthermore, the profile contains the default switches for the tools,
   1.104  hence, it must be read before the command line switches are processed.
   1.105  .P
   1.106  For historic reasons, some MH tools did not read the profile and context.
   1.107 @@ -3357,10 +3364,10 @@
   1.108  .Pn slocal .
   1.109  The reason why these tools ignored the profile were not clearly stated.
   1.110  During the discussion on the nmh-workers mailing list,
   1.111 +David Levine posted an explanation, quoting John Romine:
   1.112  .[
   1.113  nmh-workers levine post profile
   1.114  .]
   1.115 -David Levine posted an explanation, quoting John Romine:
   1.116  .QS
   1.117  I asked John Romine and here's what he had to say, which
   1.118  agrees and provides an example that convinces me:
   1.119 @@ -3476,10 +3483,10 @@
   1.120  Then Rose's motivation behind the decision that
   1.121  .Pn post
   1.122  ignores the profile, as quoted by Jeffrey Honig,
   1.123 +would have become possible:
   1.124  .[
   1.125  nmh-workers post profile
   1.126  .]
   1.127 -would have become possible:
   1.128  .QS
   1.129  when you run mh commands in a script, you want all the defaults to be
   1.130  what the man page says.
   1.131 @@ -3976,7 +3983,7 @@
   1.132  I learned about the easy and the difficult parts.
   1.133  Code is easy to understand if the influenced code area is small
   1.134  and its boundaries are strictly defined.
   1.135 -Further more, the code needs to solve the problem in a straight-forward way.
   1.136 +Furthermore, the code needs to solve the problem in a straight-forward way.
   1.137  .P
   1.138  .\" XXX move this paragraph somewhere else?
   1.139  Reading
   1.140 @@ -4019,6 +4026,7 @@
   1.141  .P
   1.142  But the real problem is another:
   1.143  Nmh violates the golden ``one tool, one job'' rule of the Unix philosophy.
   1.144 +.\" XXX ref
   1.145  Understanding
   1.146  .Pn comp
   1.147  requires understanding
   1.148 @@ -4068,6 +4076,7 @@
   1.149  No longer should we sacrifice readability or conceptional beauty.
   1.150  No longer should we violate the Unix philosophy's ``one tool, one job''
   1.151  guideline.
   1.152 +.\" XXX ref
   1.153  No longer should we keep speed improvements that became unnecessary.
   1.154  .P
   1.155  Therefore, mmh's