Gitiles
Code Review Sign In
review.blissroms.org / platform_external_nano / f1171c3c0e858e38dd909bb983982d6ccb6792f1 / . / faq.html
blob: b98565c0fd930dfb46d8736264b6128ca1b4eaac [file] [log] [blame]
Chris Allegretta065bb1e2000-07-23 16:09:33 +0000[diff] [blame]1<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
2<html>
3<head>
4 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
5 <meta name="GENERATOR" content="Mozilla/4.73 [en] (X11; U; Linux 2.2.16 i586) [Netscape]">
6</head>
7<body text="#000000" bgcolor="#FFFFFF" link="#0000EF" vlink="#51188E" alink="#FF0000">
8
9<h1>
10<font color="#CC0000">The nano FAQ</font></h1>
11<h2>
12<font color="#330000">Table of Contents</font></h2>
13
14<h2>
15<font color="#330000"><a href="#1">1.&nbsp; General</a></font></h2>
16
17<blockquote><font color="#330000"><a href="#1.1">1.1 About this FAQ.</a></font>
18<br><font color="#330000"><a href="#1.2">1.2. How do I contribute to it?</a></font>
19<br><font color="#330000"><a href="#1.3">1.3. What is nano?</a></font>
20<br><font color="#330000"><a href="#1.4">1.4. What is the history behind
21nano?</a></font>
22<br><font color="#330000"><a href="#1.5">1.5. Why the name change from
23TIP?</a></font>
24<br><font color="#330000"><a href="#1.6">1.6 What is the current version
25of nano?</a></font>
26<br><font color="#330000"><a href="#1.7">1.7. I want to read the man page
27without having to download the program!</a></font></blockquote>
28
29<h2>
30<font color="#330000"><a href="#2">2. Where to get nano</a></font></h2>
31
32<blockquote><font color="#330000"><a href="#2.1">2.1. FTP and WWW sites
33that carry nano.</a></font>
34<br><font color="#330000"><a href="#2.2">2.2. Redhat and derivatives (.rpm)
35packages.</a></font>
36<br><font color="#330000"><a href="#2.3">2.3. Debian (.deb) packages.</a></font>
37<br><font color="#330000"><a href="#2.4">2.4. By CVS (for the brave).</a></font></blockquote>
38
39<h2>
40<font color="#330000"><a href="#3">3. Installation and Configuration</a></font></h2>
41
42<blockquote><font color="#330000"><a href="#3.1">3.1. How do install the
43RPM or DEB package?</a></font>
44<br><font color="#330000"><a href="#3.2">3.2. Compiling from source: WHAT
45THE HECK DO I DO NOW?</a></font>
46<br><font color="#330000"><a href="#3.2">3.3. Why does everything go into
47/usr/local?</a></font>
48<br><font color="#330000"><a href="#3.4">3.4. I get errors about 'bindtextdomain',
49'gettext' and/or 'gettextdomain'.&nbsp; What can I do about it?</a></font></blockquote>
50
51<h2>
52<font color="#330000"><a href="#4">4. Running</a></font></h2>
53
54<blockquote><font color="#330000"><a href="#4.1">4.1. Ack!&nbsp; My backspace/delete/enter/double
55bucky/meta key doesn't seem to work!&nbsp; What can I do?</a></font>
56<br><font color="#330000"><a href="#4.2">4.2. Nano crashes when I type
57&lt;insert keystroke here>!</a></font>
58<br><font color="#330000"><a href="#4.3">4.3. Nano crashes when I resize
59my window.&nbsp;&nbsp; How can I fix that?</a></font>
60<br><font color="#330000"><a href="#4.4">4.4. Why does nano show ^\ and
61^_ in the shortcut list instead of ^G and ^J?</a></font>
62<br><a href="#4.5">4.5 How do I make nano my default editor (in Pine, mutt,
63etc.)?</a></blockquote>
64
65<h2>
66<font color="#330000"><a href="#5">5. Internationalization</a></font></h2>
67
68<blockquote><font color="#330000"><a href="#5.1">5.1. There's no translation
69for my language!</a></font>
70<br><font color="#330000"><a href="#5.2">5.2. I don't like the translation
71for &lt;x> in my language.&nbsp;&nbsp; How can I fix it?</a></font></blockquote>
72
73<h2>
74<font color="#330000"><a href="#7">6. Advocacy and Licensing</a></font></h2>
75
76<blockquote><font color="#330000"><a href="#6.1">6.1. Why should I use
77nano instead of Pico?</a></font>
78<br><font color="#330000"><a href="#6.2">6.2. Why should I use Pico instead
79of nano?</a></font>
80<br><font color="#330000"><a href="#6.3">6.3. What is so bad about the
81PINE license?</a></font>
82<br><font color="#330000"><a href="#6.4">6.4. Okay, well what mail program
83should I use then?</a></font>
84<br><font color="#330000"><a href="#6.5">6.5. Why doesn't UW simply change
85their license?</a></font>
86<br><font color="#330000"><a href="#6.6">6.6. What if tomorrow UW changes
87the license to be truly Free Software?</a></font></blockquote>
88
89<h2>
90<font color="#330000"><a href="#7">7. Miscellaneous</a></font></h2>
91
92<blockquote><font color="#330000"><a href="#7.1">7.1. Nano related mailing
93lists.</a></font>
94<br><font color="#330000"><a href="#7.2">7.2. I want to send the development
95team a big load of cash (or just a thank you).</a></font>
96<br><font color="#330000"><a href="#7.3">7.3. How do I submit a patch?</a></font>
97<br><font color="#330000"><a href="#7.4">7.4. How do I join the development
98team?</a></font>
99<br><font color="#330000"><a href="#7.5">7.5. Can I have CVS write access?</a></font></blockquote>
100
101<h2>
102<a href="#8">8. ChangeLog</a></h2>
103
104<hr WIDTH="100%">
105<br>&nbsp;
106<h1>
107<a NAME="1"></a><font color="#330000">1.&nbsp; General</font></h1>
108
109<h2>
110<a NAME="1.1"></a><font color="#330000">1.1 About this FAQ.</font></h2>
111
112<blockquote><font color="#330000">This FAQ was written and is maintained
113by Chris Allegretta &lt;<a href="mailto:chrisa@asty.org">chrisa@asty.org</a>>,
114who also happens to be the creator of nano.&nbsp;&nbsp; Maybe someone else
115will volunteer to maintain this FAQ someday, who knows...</font></blockquote>
116
117<h2>
118<a NAME="1.2"></a><font color="#330000">1.2. How do I contribute to it?</font></h2>
119
120<blockquote><font color="#330000">Your best bet is to send it to the nano
121email address, <a href="mailto:nano@asty.org">nano@asty.org</a> and if
122it is useful enough it will be included in future versions.</font></blockquote>
123
124<h2>
125<a NAME="1.3"></a><font color="#330000">1.3. What is nano?</font></h2>
126
127<blockquote><font color="#330000">Nano is designed to be a free replacement
128for the Pico text editor, part of the PINE email suite from <a href="http://www.washington.edu/pine">The
129University of Washington</a>.&nbsp; It aims to "emulate Pico as closely
130as possible and perhaps include extra functionality WITHOUT breaking compatibility
131with Pico.</font></blockquote>
132
133<h2>
134<a NAME="1.4"></a><font color="#330000">1.4. What is the history behind
135nano?</font></h2>
136
137<blockquote><font color="#330000">Funny you should ask!</font>
138<p><b><font color="#330000">In the beginning...</font></b>
139<p><font color="#330000">For years Pine was THE program used to read email
140on a Unix system.&nbsp; The Pico text editor is the portion of the program
141one would use to compose his or her mail messages.&nbsp; Many beginners
142to Unix flocked to Pico and Pine because of their well organized, easy
143to use interfaces.&nbsp; With the proliferation of Linux in the mid to
144late 90's, many University students became intimately familiar with the
145strengths (and weaknesses) of Pine and Pico.</font>
146<p><b><font color="#330000">Then came debian...</font></b>
147<p><font color="#330000">The <a href="http://www.debian.org">debian GNU/Linux</a>
148distribution, known for its strict standards in distributing truly "free"
149software (i.e. had no restrictions on redistribution), would not include
150a binary package for Pine or Pico.&nbsp; Many people had a serious dilemma:&nbsp;
151they loved these programs, but they were not truly free software in the
152<a href="http://www.gnu.org/philosophy/free-sw.html">GNU</a>
153sense of the word.</font>
154<p><b><font color="#330000">The event...</font></b>
155<p><font color="#330000">It was in late 1999 when Chris Allegretta (our
156hero) was yet again complaining to himself about the less-than-perfect
157license Pico was distributed under, the 10000 makefiles that came with
158it and how just a few small improvements could make it the Best Editor
159in the World (TM).&nbsp; Having been a convert from Slackware to debian,
160he missed having a simple binary package that included Pine and Pico, and
161had grown tired of downloading them himself.</font>
162<p><font color="#330000">Finally something snapped inside and Chris coded
163and hacked like a madman for many hours straight one weekend to make a
164(barely usable) Pico clone, at the time called TIP (Tip Isn't Pico).&nbsp;
165The program could not be invoked without a filename, could not save files,
166had no help menu, spell checker, and so forth.&nbsp; But over time it improved,
167and with the help of a few great coders it matured to the almost stable
168state it is today.</font></blockquote>
169
170<h2>
171<a NAME="1.5"></a><font color="#330000">1.5. Why the name change from TIP?</font></h2>
172
173<blockquote><font color="#330000">On January 10, 2000, TIP was officially
174renamed to nano because of a namespace conflict with another program called
175'tip'.&nbsp; The original 'tip' program "establishes a full duplex terminal
176connection to a remote host", and was included with many older Unix systems
177(and newer ones like Solaris). The conflict was not noticed at first because
178there is no 'tip' utility included with most Linux distributions (where
179nano was developed).</font></blockquote>
180
181<h2>
182<a NAME="1.6"></a><font color="#330000">1.6 What is the current version
183of nano?</font></h2>
184
185<blockquote><font color="#330000">The current version of nano *should*
Chris Allegrettaedebbe62000-07-23 16:45:20 +0000[diff] [blame]186be 0.9.13.&nbsp; Of course you should always check the nano hompage to
Chris Allegretta065bb1e2000-07-23 16:09:33 +0000[diff] [blame]187see what the latest and greatest version is.</font></blockquote>
188
189<h2>
190<a NAME="1.7"></a><font color="#330000">1.7. I want to read the man page
191without having to download the program!</font></h2>
192
193<blockquote><font color="#330000">Jeez, demanding, aren't we?&nbsp;&nbsp;
194Okay, look <a href="http://www.asty.org/nano/dist/nano.1.html">here</a>.</font></blockquote>
195
196<hr WIDTH="100%">
197<h1>
198<a NAME="2"></a><font color="#330000">2. Where to get nano</font></h1>
199
200<h2>
201<a NAME="2.1"></a><font color="#330000">2.1. FTP and WWW sites that carry
202nano.</font></h2>
203
204<blockquote><font color="#330000">The nano distribution can be downloaded
205at the following fine web and ftp sites:</font>
206<ul>
207<li>
208<font color="#330000"><a href="http://www.asty.org/nano/dist">http://www.asty.org/nano/dist</a></font></li>
209
210<li>
211<font color="#330000"><a href="http://www.ewtoo.org/~astyanax/nano/dist">http://www.ewtoo.org/~astyanax/nano/dist</a></font></li>
212
213<li>
214<font color="#330000"><a href="ftp://ftp.asty.org/pub/nano">ftp://ftp.asty.org/pub/nano</a></font></li>
215
216<li>
217<font color="#330000"><a href="ftp://nano.sourceforge.net/pub/nano/">ftp://nano.sourceforge.net/pub/nano</a></font></li>
218</ul>
219</blockquote>
220
221<h2>
222<a NAME="2.2"></a><font color="#330000">2.2. Redhat and derivatives (.rpm)
223packages.</font></h2>
224
225<blockquote>
226<ul>
227<li>
228<font color="#330000"><a href="http://www.asty.org/nano/dist/RPMS">http://www.asty.org/nano/dist/RPMS</a></font></li>
229
230<li>
231<font color="#330000"><a href="http://www.ewtoo.org/~astyanax/nano/dist/RPMS">http://www.ewtoo.org/~astyanax/nano/dist/RPMS</a></font></li>
232
233<li>
234<font color="#330000"><a href="ftp://ftp.asty.org/pub/nano/RPMS">ftp://ftp.asty.org/pub/nano/RPMS</a></font></li>
235
236<li>
237<font color="#330000"><a href="ftp://nano.sourceforge.net/pub/nano/RPMS">ftp://nano.sourceforge.net/pub/nano/RPMS</a></font></li>
238</ul>
239<font color="#330000">Additionally, check out the Redhat contribs section
240at:</font>
241<ul>
242<li>
243<font color="#330000"><a href="http://metalab.unc.edu/pub/Linux/distributions/redhat/contrib/libc6/i386">http://metalab.unc.edu/pub/Linux/distributions/redhat/contrib/libc6/i386</a></font></li>
244
245<li>
246<font color="#330000"><a href="ftp://metalab.unc.edu/pub/Linux/distributions/redhat/contrib/libc6/i386">ftp://metalab.unc.edu/pub/Linux/distributions/redhat/contrib/libc6/i386</a></font></li>
247</ul>
248</blockquote>
249
250<h2>
251<a NAME="2.3"></a><font color="#330000">2.3. Debian (.deb) packages.</font></h2>
252
253<blockquote><font color="#330000">For debian users, you can check out the
254current nano packages for:</font>
255<ul>
256<li>
257<font color="#330000"><a href="http://www.debian.org/Packages/frozen/editors/nano.html">frozen</a></font></li>
258
259<li>
260<font color="#330000"><a href="http://www.debian.org/Packages/unstable/editors/nano.html">unstable</a></font></li>
261</ul>
262<font color="#330000">Note that versions &lt; 0.9.10 are probably not for
263those wanting to get serious work done, so until the frozen/stable distributions
264have an updated version of nano, you are best off using the one in unstable
265for now.</font></blockquote>
266
267<h2>
268<a NAME="2.4"></a><font color="#330000">2.4. By CVS (for the brave).</font></h2>
269
270<blockquote><font color="#330000">For the 'bleeding edge' current version
271of nano, you can use CVS to download the current source code.&nbsp; <b>Note:</b>
272believe it or not, by downloading code that has not yet stabilized into
273an official release, there could quite possibly be bugs, in fact the code
274may not even compile!&nbsp; Anyway, see <a href="https://sourceforge.net/cvs/?group_id=1304">the
275nano CVS page</a> for info on anonymous CVS access to the nano source.</font></blockquote>
276
277<hr WIDTH="100%">
278<h1>
279<a NAME="3"></a><font color="#330000">3. Installation and Configuration</font></h1>
280
281<h2>
282<a NAME="3.1"></a><font color="#330000">3.1. How do install the RPM or
283DEB package?</font></h2>
284
285<blockquote><font color="#330000">It's simple really!&nbsp; As root, type
286<b>rpm
287-Uvh nano-x.y.z-1.i386.rpm</b> if you have a Redhat-ish system or
288<b>dpkg
289-i nano_x.y.z-1.deb</b> if you have a Debian-ish system, where
290<b>x.y.z</b>
291is the release of nano.&nbsp; There are other programs to install programs,
292and if you wish to use those, knock yourself out.</font></blockquote>
293
294<h2>
295<a NAME="3.2"></a><font color="#330000">3.2. Compiling from source: WHAT
296THE HECK DO I DO NOW?</font></h2>
297
298<blockquote><font color="#330000">Okay, take a deep breath, this really
299isn't hard.&nbsp; Unpack the nano source with a command like:</font>
300<p><b><font color="#330000">tar -zxvf nano-x.y.z.tar.gz</font></b>
301<p><font color="#330000">If you get error messages about the -z option,
302try this:</font>
303<p><b><font color="#330000">gunzip -d nano-x.y.z.tar.gz | tar xvf -</font></b>
304<p><font color="#330000">(again, where x.y.z is the version number in question).&nbsp;
305Then you need to run configure with any options you might want (if any).</font>
306<p><font color="#330000">The average case is this:</font>
307<p><b><font color="#330000">./configure</font></b>
308<br><b><font color="#330000">make</font></b>
309<br><font color="#330000"><b>make install </b>(as root, of course)</font></blockquote>
310
311<h2>
312<a NAME="3.3"></a><font color="#330000">3.3. Why does everything go into
313/usr/local?</font></h2>
314
315<blockquote><font color="#330000">Well, that's what the <b>configure</b>
316script defaults to.&nbsp; If you wish to change this, simply do this:</font>
317<p><b><font color="#330000">./configure --prefix=/usr</font></b>
318<p><font color="#330000">to put nano into /usr/bin when you run <b>make
319install</b>.</font></blockquote>
320
321<h2>
322<a NAME="3.4"></a><font color="#330000">3.4. I get errors about 'bindtextdomain',
323'gettext' and/or 'gettextdomain'.&nbsp; What can I do about it?</font></h2>
324
325<blockquote><font color="#330000">Try doing a <b>./configure --with-included-gettext</b>
326and see if that solves your problem.&nbsp; You make need to do a <b>make
327clean ; make</b> to get it to work fully.</font></blockquote>
328
329<hr WIDTH="100%">
330<h1>
331<a NAME="4"></a><font color="#330000">4. Running</font></h1>
332
333<h2>
334<a NAME="4.1"></a><font color="#330000">4.1. Ack!&nbsp; My backspace/delete/enter/double
335bucky/meta key doesn't seem to work!&nbsp; What can I do?</font></h2>
336
337<blockquote><font color="#330000">Try setting your $TERM variable to 'vt100'.&nbsp;
338Nano doesn't yet support every term entry under the sun.</font>
339<p><font color="#330000">Bourne shell users (like bash): <b>export TERM=vt100</b></font>
340<br><font color="#330000">C Shell users (tcsh and csh): <b>setenv TERM
341vt100</b></font></blockquote>
342
343<h2>
344<a NAME="4.2"></a><font color="#330000">4.2. Nano crashes when I type &lt;insert
345keystroke here>!</font></h2>
346
347<blockquote><font color="#330000">If you aren't trying some bizarre keystroke
348combination with some bizarre $TERM entry, chances are you have found a
349bug.&nbsp;&nbsp; You are welcome to submit it to the nano-devel list or
350to <a href="mailto:nano@asty.org">nano@asty.org</a>.</font></blockquote>
351
352<h2>
353<a NAME="4.3"></a><font color="#330000">4.3. Nano crashes when I resize
354my window.&nbsp;&nbsp; How can I fix that?</font></h2>
355
356<blockquote><font color="#330000">Older versions of nano had this problem,
357please upgrade to a newer version (at least 0.9.9 would be great, 0.9.
35812 is recommended).</font></blockquote>
359
360<h2>
361<a NAME="4.4"></a><font color="#330000">4.4. Why does nano show ^\ and
362^_ in the shortcut list instead of ^G and ^J?</font></h2>
363
364<blockquote><font color="#330000">The help (^G) and justify (^J) functions
365were among the last to be written.&nbsp; To show the improvements that
366nano had over Pico (goto line # and replace), ^_ and ^\ were put on the
367shortcut list.&nbsp;&nbsp; If you use the <b>-p</b> option to nano you
368will get the same shortcuts at the bottom as Pico.</font></blockquote>
369
370<h2>
371<a NAME="4.5"></a>4.5 How do I make nano my default editor (in Pine, mutt,
372etc)?</h2>
373
374<blockquote>You need to make nano your $EDITOR.&nbsp; If you want this
375to be saved, you should put a line like this in your <b>.bashrc</b> if
376you use bash:
377<p><b>export EDITOR=/usr/local/bin/nano</b>
378<p>or if you use tcsh put this in your <b>.cshrc</b> file:
379<p><b>setenv EDITOR /usr/local/bin/nano</b>
380<p>Change /usr/local/bin/nano to wherever nano is installed in your system.&nbsp;
381Type which nano to find out. This will not take effect until the next time
382you login.&nbsp; So log out and back in again.
383<p>Then on top that if you use Pine you must go into setup (type <b>S</b>
384at the main menu), then configure (type <b>C</b>).&nbsp; Hit enter on the
385lines that say:
386<p><b>[ ]&nbsp; enable-alternate-editor-cmd</b>
387<br><b>[ ]&nbsp; enable-alternate-editor-implicitly</b>
388<p>Then exit (<b>E</b>) and select Yes (<b>Y</b>).
389<p>Mutt users should see an effect immediately the next time you log in,
390no further configuration is needed.&nbsp; However, if you want to let people
391know you use nano to compose your email messages, you can put a line like
392this in your <b>.muttrc</b>:
393<p><b>my_hdr X-Composer: nano x.y.z</b>
394<p>Again, replace x.y.z with the version of nano you use.
395<br>&nbsp;</blockquote>
396
397<hr WIDTH="100%">
398<h1>
399<a NAME="5"></a><font color="#330000">5. Internationalization</font></h1>
400
401<h2>
402<a NAME="5.1"></a><font color="#330000">5.1. There's no translation for
403my language!</font></h2>
404
405<blockquote><font color="#330000">So, uh, get someone who speaks your native
406language to write one =-).&nbsp; Just grab the <b>nano.pot</b> file from
407the latest and greatest nano distribution (it's in the <b>po/</b> directory)
408and translate each line into your native language on the <b>msgstr</b>
409line.&nbsp; Then send it to the nano devel list or <a href="mailto:nano@asty.org">nano@asty.org</a>.</font></blockquote>
410
411<h2>
412<a NAME="5.2"></a><font color="#330000">5.2. I don't like the translation
413for &lt;x> in my language.&nbsp;&nbsp; How can I fix it?</font></h2>
414
415<blockquote><font color="#330000">The best way would probably be to e-mail
416the person listed in the <b>&lt;your_language>.po</b> file with your suggested
417corrections and they can in turn forward it to the nano email address,
418or the devel list.</font></blockquote>
419
420<hr WIDTH="100%">
421<h1>
422<a NAME="6"></a><font color="#330000">6. Advocacy and Licensing</font></h1>
423
424<h2>
425<a NAME="6.1"></a><font color="#330000">6.1. Why should I use nano instead
426of Pico?</font></h2>
427
428<blockquote><font color="#330000">There are many reasons to use nano instead
429of Pico, a more complete list can be found at the <a href="http://www.asty.org/nano">nano
430homepage</a>.</font></blockquote>
431
432<h2>
433<a NAME="6.2"></a><font color="#330000">6.2. Why should I use Pico instead
434of nano?</font></h2>
435
436<blockquote>Again, check out the <a href="http://www.asty.org/nano">nano
437homepage</a> for a good summary of reasons.&nbsp; It really is a matter
438of personal preference as to which editor you should use.&nbsp; If you're
439the type of person who likes using the original version of a program, then
440Pico is the editor for you.&nbsp;&nbsp; If you're looking for a few more
441features and a 'better' license as far as adding your own changes (sacrificing
442mailer integration and a little stability), nano is the way to go.</blockquote>
443
444<h2>
445<a NAME="6.3"></a><font color="#330000">6.3. What is so bad about the PINE
446license?</font></h2>
447
448<blockquote><font color="#330000">Technically there is nothing "wrong"
449with the U of W license for Pine and Pico.&nbsp; However, it is&nbsp; not
450considered truly "free" according to the <a href="http://www.debian.org/social_contract#guidelines">Debian
451Free Software Guidelines</a>.&nbsp; The only real problem as far as I'm
452aware as that there are limitations on the redistribution of programs based
453on the Pine and Pico source.&nbsp;&nbsp; So at a real nitty gritty level,
454these programs are not considered Free Software.&nbsp; This is why Pico
455isn't distributed in binary form in debian, and hence one of the main reasons
456nano was started.</font></blockquote>
457
458<h2>
459<a NAME="6.4"></a><font color="#330000">6.4. Okay, well what mail program
460should I use then?</font></h2>
461
462<blockquote><font color="#330000">Well, there is nothing stopping you from
463using Pine with nano (or Pine with Pico for that matter).&nbsp; But if
464you want to use programs that are considered Free Software, you may want
465to look into <a href="http://www.mutt.org">mutt</a>.&nbsp; It is a full-screen,
466console based mail program that actually has a lot more flexibility than
467Pine, but has a keymap included in the distribution that allows you to
468use the same keystrokes as Pine would to send and receive mail.&nbsp; It's
469also licensed under the GPL.</font></blockquote>
470
471<h2>
472<a NAME="6.5"></a><font color="#330000">6.5. Why doesn't UW simply change
473their license?</font></h2>
474
475<blockquote><font color="#330000">You're really not asking the right person
476here.&nbsp; I (Chris) waited along time to see if UW would change their
477license because of the amount of high quality software being released and
478developed under the GPL without being taken advantage of by malicious corporate
479entities or other baddies, but no such luck so far.</font></blockquote>
480
481<h2>
482<a NAME="6.6"></a><font color="#330000">6.6. What if tomorrow UW changes
483the license to be truly Free Software?</font></h2>
484
485<blockquote><font color="#330000">Honestly nothing would make me happier
486than to see that happen.&nbsp; Nano would continue to be developed independently
487until such time as Pico had all the features nano did or the projects merged.&nbsp;
488That just does not seem very likely given that there has been no sign of
489any changes in the past few years in a positive direction.</font></blockquote>
490
491<hr WIDTH="100%">
492<h1>
493<a NAME="7"></a><font color="#330000">7. Miscellaneous</font></h1>
494
495<h2>
496<a NAME="7.1"></a><font color="#330000">7.1. Nano related mailing lists.</font></h2>
497
498<blockquote><font color="#330000">There are two mailing lists for nano
499hosted at <a href="http://www.sourceforge.net">SourceForge</a>, nano-announce
500and nano-devel.&nbsp; Nano-announce is a very low traffic list where new
501versions of nano are announced (surprise!)&nbsp; Nano-devel is a sometimes
502low, sometimes very high traffic list for dicussing the present and future
503development of nano.&nbsp; Here are links to where you can sign up for
504a given list:</font><font color="#330000"></font>
505<p><font color="#330000">nano-announce - <a href="http://lists.sourceforge.net/mailman/listinfo/nano-announce">http://lists.sourceforge.net/mailman/listinfo/nano-announce</a></font>
506<br><font color="#330000">nano-devel - <a href="http://lists.sourceforge.net/mailman/listinfo/nano-devel">http://lists.sourceforge.net/mailman/listinfo/nano-devel</a></font></blockquote>
507
508<h2>
509<a NAME="7.2"></a><font color="#330000">7.2. I want to send the development
510team a big load of cash (or just a thank you).</font></h2>
511
512<blockquote><font color="#330000">That's fine.&nbsp; Send it <a href="mailto:nano-devel@lists.sourceforge.net">our
513way</a>!&nbsp; Better yet, fix a <a href="http://www.asty.org/nano/dist/BUGS">bug</a>
514in the program or implement a <a href="http://www.asty.org/nano/dist/TODO">cool
515feature</a> and send us that instead (though cash is fine too).</font></blockquote>
516
517<h2>
518<a NAME="7.3"></a><font color="#330000">7.3. How do I submit a patch?</font></h2>
519
520<blockquote><font color="#330000">See Section <a href="#7.2">7.2</a>.</font></blockquote>
521
522<h2>
523<a NAME="7.4"></a><font color="#330000">7.4. How do I join the development
524team?</font></h2>
525
526<blockquote><font color="#330000">The easiest way is to consistently send
527in good patches that add some needed functionality, fix a bug or two and/or
528make the program more optimized/efficient.&nbsp; Then ask nicely and you
529will probably be added to the SourceForge development list and be given
530CVS write after awhile.&nbsp; There is a lot of responsibility that goes
531along with being a team member, so don't think it's just something to add
532to your resume.</font></blockquote>
533
534<h2>
535<a NAME="7.5"></a><font color="#330000">7.5. Can I have CVS write access?</font></h2>
536
537<blockquote><font color="#330000">Re-read Section </font><a href="#7.4">7.4</a><font color="#330000">
538and you should know the answer.</font></blockquote>
539
540<h1>
541<a NAME="8"></a>8. ChangeLog</h1>
542
543<blockquote>06/31/2000 - Initial framework.</blockquote>
544
545</body>
546</html>