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

docs: stop implying that nano wants to be fully compatible with Pico

master
Benno Schulenberg 2019-01-22 21:20:46 +01:00
parent 4b8bd27d08
commit 6aad99bd81
4 changed files with 12 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
README
View File

@ -1,5 +1,5 @@
GNU nano -- an enhanced clone of the Pico text editor
GNU nano -- a simple editor, inspired by Pico
Overview
@ -13,9 +13,12 @@ Overview
go-to-line-number or search-and-replace) were unavailable until
recently or require a command-line flag. Yuck.
nano aims to solve these problems by emulating the functionality of
Pico as closely as possible while addressing the problems above and
providing other extra functionality.
Nano aimed to solve these problems by: 1) being truly free software
by using the GPL, 2) emulating the functionality of Pico as closely
as is reasonable, and 3) include extra functionality by default.
Nowadays, nano wants to be a generally useful editor, with default
settings that do not change the file contents automatically.
The nano editor is an official GNU package. For more information on
GNU and the Free Software Foundation, please see https://www.gnu.org/.

2
doc/faq.html
View File

@ -71,7 +71,7 @@
<h1><a name="1"></a>1. General</h1>
<h3><a name="1.1"></a>1.1. What is GNU nano?</h3>
<blockquote><p>GNU nano is designed to be a free replacement for the Pico text editor, part of the Pine email suite from <a href="http://www.washington.edu/pine/">The University of Washington</a>. It aims to &quot;emulate Pico as closely as possible and then include extra functionality&quot;.</p></blockquote>
<blockquote><p>GNU nano was designed to be a free replacement for the Pico text editor, part of the Pine email suite from <a href="http://www.washington.edu/pine/">The University of Washington</a>. It aimed to &quot;emulate Pico as closely as is reasonable and then include extra functionality&quot;.</p></blockquote>
<h3><a name="1.2"></a>1.2. What is the history behind nano?</h3>
<blockquote><p>Funny you should ask!</p>
<p><b>In the beginning...</b></p>

2
doc/nano.1
View File

@ -19,7 +19,7 @@
.TH NANO 1 "version 3.2" "November 2018"
.SH NAME
nano \- Nano's ANOther editor, an enhanced free Pico clone
nano \- Nano's ANOther editor, inspired by Pico
.SH SYNOPSIS
.B nano

6
doc/nano.texi
View File

@ -92,7 +92,7 @@ file locking, backup files, and internationalization support.
The original goal for @command{nano} was to be a complete bug-for-bug
emulation of Pico. But currently the goal is to be as compatible
as possible while offering a superset of Pico's functionality.
as is reasonable while offering a superset of Pico's functionality.
@xref{Pico Compatibility} for more details on how @command{nano} and
Pico differ.
@ -1507,8 +1507,8 @@ browser exits.
@node Pico Compatibility
@chapter Pico Compatibility
@command{nano} attempts to emulate Pico as closely as possible, but there
are some differences between the editors:
@command{nano} emulates Pico as closely as is reasonable, but there
are some differences between the two editors:
@table @code