ariadne
/
smol
2
1
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
smol/README

80 lines
2.9 KiB
Plaintext
Raw Normal View History

Initial revision git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
2000-06-06 05:53:49 +00:00
docs: stop implying that nano wants to be fully compatible with Pico
2019-01-22 20:20:46 +00:00
GNU nano -- a simple editor, inspired by Pico
1.1 version and note added to README that this is the unstable branch git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@591 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
2001-04-07 17:50:03 +00:00
Finally got rid of TIP from README and updated the Overview which people always quote from git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@430 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
2000-12-27 15:46:22 +00:00
Overview
tweaks: indenting text files with tabs is not a good idea The tabsize can vary by configuring editor or viewer, but the text has some kind of intended alignment. Also, change the indentation a bit, to make things line up more neatly.
2018-01-09 15:47:51 +00:00
The nano project was started because of a few "problems" with the
wonderfully easy-to-use and friendly Pico text editor.
Finally got rid of TIP from README and updated the Overview which people always quote from git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@430 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
2000-12-27 15:46:22 +00:00
tweaks: indenting text files with tabs is not a good idea The tabsize can vary by configuring editor or viewer, but the text has some kind of intended alignment. Also, change the indentation a bit, to make things line up more neatly.
2018-01-09 15:47:51 +00:00
First and foremost was its license: the Pine suite does not use
tweaks: reword the description of the disadvantages of Pico Also reword a list of features to exclude the ones that only make sense when contrasting nano with Pico.
2019-01-23 18:13:23 +00:00
the GPL, and (before using the Apache License) it had unclear
restrictions on redistribution. Because of this, Pine and Pico
were not included in many GNU/Linux distributions. Furthermore,
some features (like go-to-line-number or search-and-replace) were
unavailable for a long time or require a command-line flag. Yuck.
Initial revision git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
2000-06-06 05:53:49 +00:00
docs: stop implying that nano wants to be fully compatible with Pico
2019-01-22 20:20:46 +00:00
Nano aimed to solve these problems by: 1) being truly free software
by using the GPL, 2) emulating the functionality of Pico as closely
docs: adjust the wording of the README to be factually correct That is: don't say that nano doesn't change the file contents by default. Also, correct the style of the preceding paragraph.
2019-04-28 08:34:32 +00:00
as is reasonable, and 3) including extra functionality by default.
docs: stop implying that nano wants to be fully compatible with Pico
2019-01-22 20:20:46 +00:00
docs: adjust the wording of the README to be factually correct That is: don't say that nano doesn't change the file contents by default. Also, correct the style of the preceding paragraph.
2019-04-28 08:34:32 +00:00
Nowadays, nano wants to be a generally useful editor with sensible
defaults (linewise scrolling, no automatic line breaking).
Nano is now a GNU package git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@534 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
2001-02-14 14:28:27 +00:00
tweaks: indenting text files with tabs is not a good idea The tabsize can vary by configuring editor or viewer, but the text has some kind of intended alignment. Also, change the indentation a bit, to make things line up more neatly.
2018-01-09 15:47:51 +00:00
The nano editor is an official GNU package. For more information on
tweaks: change a bunch of URLs to use 'https' instead of 'http'
2018-11-11 11:28:40 +00:00
GNU and the Free Software Foundation, please see https://www.gnu.org/.
remove a few more unneeded spaces git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@1619 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
2004-01-10 06:12:04 +00:00
Initial revision git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
2000-06-06 05:53:49 +00:00
How to compile and install nano
docs: adjust for the changed name of the header-file package on Debian Also, be more complete, reword a few things, and stop mentioning Slang.
2020-10-11 14:29:40 +00:00
Download the latest nano source tarball, and then:
Fixing the explanation of how to subscribe to a mailing list. git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@5121 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
2015-02-21 09:45:53 +00:00
docs: adjust the compilation instructions to two-digit version numbers
2019-10-27 18:15:04 +00:00
tar -xvf nano-x.y.tar.gz
cd nano-x.y
tweaks: indenting text files with tabs is not a good idea The tabsize can vary by configuring editor or viewer, but the text has some kind of intended alignment. Also, change the indentation a bit, to make things line up more neatly.
2018-01-09 15:47:51 +00:00
./configure
make
make install
remove a few more unneeded spaces git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@1619 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
2004-01-10 06:12:04 +00:00
docs: adjust for the changed name of the header-file package on Debian Also, be more complete, reword a few things, and stop mentioning Slang.
2020-10-11 14:29:40 +00:00
You will need the header files of ncurses installed for ./configure
to succeed -- get them from libncurses-dev (Debian) or ncurses-devel
(Fedora) or a similarly named package. Use --prefix with ./configure
to override the default installation directory of /usr/local.
Fixing the explanation of how to subscribe to a mailing list. git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@5121 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
2015-02-21 09:45:53 +00:00
docs: adjust for the changed name of the header-file package on Debian Also, be more complete, reword a few things, and stop mentioning Slang.
2020-10-11 14:29:40 +00:00
After installation you may want to copy the doc/sample.nanorc file
to your home directory, rename it to ".nanorc", and then edit it
tweaks: indenting text files with tabs is not a good idea The tabsize can vary by configuring editor or viewer, but the text has some kind of intended alignment. Also, change the indentation a bit, to make things line up more neatly.
2018-01-09 15:47:51 +00:00
according to your taste.
remove a few more unneeded spaces git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@1619 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
2004-01-10 06:12:04 +00:00
Initial revision git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
2000-06-06 05:53:49 +00:00
Web Page
tweaks: indenting text files with tabs is not a good idea The tabsize can vary by configuring editor or viewer, but the text has some kind of intended alignment. Also, change the indentation a bit, to make things line up more neatly.
2018-01-09 15:47:51 +00:00
https://nano-editor.org/
remove a few more unneeded spaces git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@1619 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
2004-01-10 06:12:04 +00:00
docs: harmonize the indentation of the README, and tweak some wordings
2016-11-13 19:35:19 +00:00
Mailing Lists
Initial revision git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
2000-06-06 05:53:49 +00:00
tweaks: indenting text files with tabs is not a good idea The tabsize can vary by configuring editor or viewer, but the text has some kind of intended alignment. Also, change the indentation a bit, to make things line up more neatly.
2018-01-09 15:47:51 +00:00
There are three nano-related mailing-lists.
minor fixes for the README git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@1618 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
2004-01-10 06:02:05 +00:00
tweaks: indenting text files with tabs is not a good idea The tabsize can vary by configuring editor or viewer, but the text has some kind of intended alignment. Also, change the indentation a bit, to make things line up more neatly.
2018-01-09 15:47:51 +00:00
+ info-nano@gnu.org is a very low traffic list used to announce
new nano versions or other important info about the project.
docs: adjust for the changed name of the header-file package on Debian Also, be more complete, reword a few things, and stop mentioning Slang.
2020-10-11 14:29:40 +00:00
tweaks: indenting text files with tabs is not a good idea The tabsize can vary by configuring editor or viewer, but the text has some kind of intended alignment. Also, change the indentation a bit, to make things line up more neatly.
2018-01-09 15:47:51 +00:00
+ help-nano@gnu.org is for those seeking to get help without
wanting to hear about the technical details of its development.
docs: adjust for the changed name of the header-file package on Debian Also, be more complete, reword a few things, and stop mentioning Slang.
2020-10-11 14:29:40 +00:00
tweaks: indenting text files with tabs is not a good idea The tabsize can vary by configuring editor or viewer, but the text has some kind of intended alignment. Also, change the indentation a bit, to make things line up more neatly.
2018-01-09 15:47:51 +00:00
+ nano-devel@gnu.org is the list used by the people that make nano
and a general development discussion list, with moderate traffic.
docs: harmonize the indentation of the README, and tweak some wordings
2016-11-13 19:35:19 +00:00
tweaks: indenting text files with tabs is not a good idea The tabsize can vary by configuring editor or viewer, but the text has some kind of intended alignment. Also, change the indentation a bit, to make things line up more neatly.
2018-01-09 15:47:51 +00:00
To subscribe, send email to <name>-request@gnu.org with a subject
of "subscribe", where <name> is the list you want to subscribe to.
docs: harmonize the indentation of the README, and tweak some wordings
2016-11-13 19:35:19 +00:00
docs: insert links to the mailing-list archives into the README To make those archives easier to find.
2020-12-21 10:17:24 +00:00
The archives of the development and help mailing lists are here:
https://lists.gnu.org/archive/html/nano-devel/
https://lists.gnu.org/archive/html/help-nano/
docs: harmonize the indentation of the README, and tweak some wordings
2016-11-13 19:35:19 +00:00
Bug Reports
tweaks: condense the description of how to report a bug The list of bugs is quite short these days, and most of them are feature requests, so asking the user to check whether a particular problem has already been reported doesn't make much sense.
2020-12-25 15:40:51 +00:00
If you find a bug, please file a detailed description of the problem
on nano's bug tracker: https://savannah.gnu.org/bugs/?group=nano.
Initial revision git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
2000-06-06 05:53:49 +00:00
copyright: update the years, use ranges, and explain this usage The interval 2013-2017 for the Free Software Foundation is valid because in those years there were releases with changes by either Chris or David, and the GNU maintainers guide advises to mention a new year in all files of a package, not just in the ones that actually changed, and be done with it for the rest of the year.
2017-04-09 10:09:23 +00:00
Copyright Years
tweaks: indenting text files with tabs is not a good idea The tabsize can vary by configuring editor or viewer, but the text has some kind of intended alignment. Also, change the indentation a bit, to make things line up more neatly.
2018-01-09 15:47:51 +00:00
When in any file of this package a copyright notice mentions a
year range (such as 1999-2011), it is a shorthand for a list of
all the years in that interval.