Mercurial > docs > master

comparison preface.roff @ 30:d996f130e279

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Some rework and new text in the Preface.
author markus schnalke <meillo@marmaro.de>
date Wed, 09 May 2012 15:50:40 +0200
parents 6c63083b4c19
children 029e11dd4de1
comparison
equal deleted inserted replaced
29:6afbb4a49962 30:d996f130e279
8 This thesis describes creating an experimental version of nmh, 8 This thesis describes creating an experimental version of nmh,
9 named \fImmh\fP, 9 named \fImmh\fP,
10 to modernize, stream-line and to exploit the concepts 10 to modernize, stream-line and to exploit the concepts
11 even more thoroughly. 11 even more thoroughly.
12 12
13 .U2 "The Path to this Thesis 13 .U2 "Background to this Thesis
14 .P 14 .P
15 I have discovered nmh in September 2009. At that time I used to use the 15 I have discovered nmh in September 2009. At that time I used to use the
16 mail client mutt, like many command line-attracted Unix users do. 16 mail client mutt, like many command line-attracted Unix users do.
17 The concepts of nmh had convinced me at once and thus learning 17 The concepts of nmh had convinced me at once and thus learning
18 its different model of email handling had been relatively easy. 18 its different model of email handling had been relatively easy.
94 work to the present state of nmh. Time should prove me successful or 94 work to the present state of nmh. Time should prove me successful or
95 not. 95 not.
96 Nmh would hardly be hurt by my work as I would not interfere with 96 Nmh would hardly be hurt by my work as I would not interfere with
97 them. But nmh would profit from my experiences. 97 them. But nmh would profit from my experiences.
98 98
99 .U2 "Focus and Delimitation of the Document 99 .U2 "Focus of this Document
100 .P 100 .P
101 This document describes my work on the experimental version, named 101 This document describes my work on the experimental version, named
102 \fImmh\fP. It explains the changes I did to nmh, with having the focus 102 \fImmh\fP. It explains the changes I did to nmh, with having the focus
103 on the reasons for the changes. It discusses technical, historical, 103 on the reasons for the changes. It discusses technical, historical,
104 social and philosophical reasons. On the technical side, this document 104 social and philosophical reasons. On the technical side, this document
109 and experiences of a newcomer with revolutionary aims entering an old 109 and experiences of a newcomer with revolutionary aims entering an old
110 and matured software projects and its community. Finally, philosophical 110 and matured software projects and its community. Finally, philosophical
111 thoughts on style, mainly based to the Unix philosophy, are present 111 thoughts on style, mainly based to the Unix philosophy, are present
112 throughout the discussions. 112 throughout the discussions.
113 .P 113 .P
114 This document is written for the community \(en developers and users \(en 114 This document is written for the community around MH-like mail systems
115 around MH-like mail systems. 115 \(en developers and users.
116 First of all, the document shall propagade the design goals and 116 First of all, the document shall propagade the design goals and
117 implementation decisions of mmh. But as well, it shall clarify my 117 implementation decisions of mmh. But as well, it shall clarify my
118 perception of the 118 personal perception of the
119 concepts of MH and Unix, and the therefrom resulting point of view. 119 concepts of MH and Unix, and explain the therefrom resulting point of view.
120 Further more, the document shall explain this view on nmh and mmh. 120 Despite the focus on MH-like systems, this document can be worthwhile
121 Despite the focus on MH-like systems, this document can be useful
122 to anyone interested in the Unix philosophy, as well as anyone 121 to anyone interested in the Unix philosophy, as well as anyone
123 involved in old software projects, be it code-related or community-related. 122 involved in old software projects, be it code or community-related.
124 .P 123 .P
125 The reader is expected to know Unix, C and email well. Good Unix shell 124 The reader is expected to have good knowledge of Unix, C and emailing.
125 Good Unix shell
126 knowledge, including shell scripting, is required. MH relies fundamentally 126 knowledge, including shell scripting, is required. MH relies fundamentally
127 on the shell. Without the power of the shell, MH becomes a motorbike 127 on the shell. Without the power of the shell, MH becomes a motorbike
128 without winding roads. 128 without winding roads: boring.
129 Introductions to Unix and its shell can be found in XXX. 129 Introductions to Unix and its shell can be found in XXX.
130 The reader is 130 The reader is
131 expected to be familiar with the C programming language, although the 131 expected to be familiar with the C programming language, although the
132 document should be quite readable without knowledge of C, too. 132 document should be understandable without knowledge of C, too.
133 The book by Kernighan and Ritchie is the definitive guide to C. 133 The book by Kernighan and Ritchie is the definitive guide to C.
134 Some book about system-level C programming is worthwile additional 134 Some book about system-level C programming is worthwile additional
135 literature. Rochkind and Curry have written such books. 135 literature. Rochkind and Curry have written such books.
136 As large parts of the code are old, old books are likely more helpful. 136 As large parts of the code are old, old books are likely more helpful.
137 The format of email messages as well as the structure of email transfer 137 The format of email messages as well as the structure of email transfer
141 Frequent references to the Unix philosophy will be made. 141 Frequent references to the Unix philosophy will be made.
142 Gancarz XXX had tried to sum the philosophy up. Even better but less 142 Gancarz XXX had tried to sum the philosophy up. Even better but less
143 concrete is the literature by Kernighan and Pike XXX. 143 concrete is the literature by Kernighan and Pike XXX.
144 The term paper ``Why the Unix Philosophy still matters'' by myself 144 The term paper ``Why the Unix Philosophy still matters'' by myself
145 provides an overview on the topic, including a case study of MH. 145 provides an overview on the topic, including a case study of MH.
146 Although a brief introduction to MH is provided in Chapter 1, the reader
147 is encouraged to have a look at the \fIMH Book\fP by Jerry Peek.
148 It is the definitive guide to MH and nmh.
149 The current version is available freely on the Internet XXX.
150 .P
151 This document is neither a user's tutorial to mmh nor an introduction
152 to any of the topics covered. It contains discussions on Unix, email
153 and system design on an advanced level.
154 However, as knowledge of the fundamental concepts is the most valuable
155 information over some program or software system a user can aquire,
156 this document might be worth a read for non-developers too.
146 157
147 158
148 .U2 "Organization 159 .U2 "Organization
149 .P 160 .P
150 Which font for what use. 161 Which font for what use.
169 To be written at the very end. 180 To be written at the very end.
170 181
171 182
172 .\" End or Preface. Start of the normal text. 183 .\" End or Preface. Start of the normal text.
173 .\" Switch to arabic page numbers and start on a right page. 184 .\" Switch to arabic page numbers and start on a right page.
185 .
174 .if e \{ 186 .if e \{
175 . pn 1 187 . pn 1
176 . af PN 1 188 . af PN 1
177 .\} 189 .\}
178 .if o \{ 190 .if o \{