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