docs/master

annotate future.roff @ 135:d8adac1ed7d8

Don't refer as long as we don't have the reference in the database. This prevents warnings.
author markus schnalke <meillo@marmaro.de>
date Tue, 03 Jul 2012 22:31:38 +0200
parents 8c56dac46efe
children e042616ad3a2
rev   line source
meillo@132 1 .H0 "Future of mmh
meillo@132 2 .P
meillo@0 3
meillo@132 4
meillo@132 5 .U2 "Summary
meillo@132 6 .P
meillo@132 7
meillo@132 8 .P
meillo@132 9 The far most difficult improvements, but at the same time the most
meillo@132 10 valuable ones.
meillo@132 11
meillo@132 12 .P
meillo@132 13 Although I did only a small part of the draft handling improvement,
meillo@132 14 I value it as an important part.
meillo@132 15
meillo@132 16 .QS
meillo@132 17 It seems that perfection is attained not when there is nothing
meillo@132 18 more to add, but when there is nothing more to remove.
meillo@132 19 .QE
meillo@132 20 antoine de saint exupery: Wind, Sand and Stars (1939)
meillo@132 21
meillo@132 22
meillo@132 23
meillo@132 24
meillo@132 25
meillo@132 26 .U2 "Outlook
meillo@132 27 .P
meillo@132 28
meillo@132 29 .P
meillo@132 30 MIME Integration:
meillo@132 31 user-visible access to whole messages and MIME parts are inherently
meillo@132 32 different
meillo@132 33
meillo@132 34
meillo@132 35
meillo@132 36
meillo@132 37 .U2 "Relationship to nmh
meillo@132 38 .P
meillo@0 39 .P
meillo@42 40 Because of several circumstances, my experimental version is rather
meillo@42 41 a fork today, although this may change again in the future.
meillo@0 42
meillo@0 43 .P
meillo@53 44 Although mmh bases on nmh, it is likely seen as a step backward.
meillo@53 45 I agree.
meillo@53 46 However, this step backward actually is a step forward,
meillo@53 47 although in a different direction.
meillo@53 48
meillo@132 49
meillo@53 50 .P
meillo@53 51 .\" Top candidate for the final sentence:
meillo@53 52 This enabled me to follow my vision straightly and thus produce
meillo@53 53 a result of greater pureness.