nano

nano with my custom patches
git clone git://bsandro.tech/nano
Log | Files | Refs | README | LICENSE

commit 78eb483bc24066cc4d0119cde17c32537a58e49e
parent c7033324a9e31d7b00454db04496880e889d32f0
Author: Benno Schulenberg <bensberg@telfort.nl>
Date:   Wed,  2 Apr 2025 09:23:41 +0200

bump version numbers and add a news item for the 8.4 release

Diffstat:
MChangeLog | 49+++++++++++++++++++++++++++++++++++++++++++++++++
MNEWS | 6++++++
MREADME | 2+-
Mconfigure.ac | 2+-
Mdoc/faq.html | 2+-
Mdoc/nano.1 | 2+-
Mdoc/nano.texi | 8++++----
Mdoc/nanorc.5 | 2+-
Mdoc/rnano.1 | 2+-
Mroll-a-release.sh | 2+-
10 files changed, 66 insertions(+), 11 deletions(-)

diff --git a/ChangeLog b/ChangeLog @@ -1,3 +1,52 @@ +Changes between v8.3 and v8.4: +------------------------------ + +Benno Schulenberg (40): + bump version numbers and add a news item for the 8.4 release + copyright: update the years for the FSF + docs: add a suggestion to the FAQ on how to configure nano for git + docs: change two interface colors in the sample nanorc + docs: improve the description of the `constantshow` bindable function + docs: in the FAQ, replace an old item with an item about Byte Order Marks + docs: replace a word that is better not used in the plural + docs: use proper emdashes instead of double hyphens: "--" => "\(em" + execute: retain what the user typed before a tool was invoked + feedback: warn when the cursor sits on a Byte Order Mark (BOM) + gnulib: update to its current upstream state + input: adjust file browser and help viewer for changed bracketed pastes + input: implement bracketed pastes in a different manner + input: make bracketed paste more robust against loss of closing sequence + input: remove a special-case workaround + input: remove single-keycode detection from the bracketed-paste routine + input: robustness is good, but dropping a key code is not a good idea + input: wait a bit for "~" when bracketed-paste sequence is incomplete + prompt: accept tabs in an external paste as literal tabs + prompt: beep when an external paste contains a command code + syntax: groff: highlight the zeroeth macro argument too + syntax: man: highlight some escapes, like \& and \(em, specially + syntax: po: colorize also a 'msgctxt' line, and the 'c++-format' flag + syntax: po: colorize also format specifiers like "%.6f" + syntax: po: colorize also format specifiers like "%<PRIu64>" + syntax: po: colorize also Python's "%(name)x" format specifiers + syntax: po: colorize also the %llu and %hhi format specifiers + syntax: po: colorize also the Python-specific conversion specifier "%r" + tweaks: add a translator hint for the three changed file-writing prompts + tweaks: add missing closing quotes, as reported by `mandoc -T lint ...` + tweaks: avoid running tolower() on an out-of-range value + tweaks: change the man-page markup of options that take an argument + tweaks: condense a fragment of code + tweaks: consistently use "\fR" for switching back to normal, roman font + tweaks: prevent some color keywords from getting hyphenated in man page + tweaks: prevent some more keywords from getting hyphenated + tweaks: remove an unwanted newline from a debugging message + tweaks: remove three redundant pairs of parentheses from a nanorc regex + tweaks: remove two commented-out lines and two unused variables + tweaks: swap two fragments of code, to allow unwrapping a line + +Brand Huntsman (1): + files: improve the wording of the normal file-writing prompts + + Changes between v8.2 and v8.3: ------------------------------ diff --git a/NEWS b/NEWS @@ -1,3 +1,9 @@ +2025.04.02 - GNU nano 8.4 "Five Miles Out" +• Bracketed pastes over a slow connection are more reliable. +• Tabs in an external paste at a prompt are not dropped. +• Feedback occurs when the cursor sits on a Byte Order Mark. +• The Execute prompt is more forgiving of a typo. + 2024.12.21 - GNU nano 8.3 "like mice in the dream of a tabby cat" • A build failure with gcc-15 is fixed. • Several translations were updated. diff --git a/README b/README @@ -15,7 +15,7 @@ Appearance In rough ASCII graphics, this is what nano's screen looks like: ____________________________________________________________________ - | GNU nano 8.3 filename Modified | + | GNU nano 8.4 filename Modified | -------------------------------------------------------------------- | This is the text window, displaying the contents of a 'buffer', | | the contents of the file you are editing. | diff --git a/configure.ac b/configure.ac @@ -16,7 +16,7 @@ # You should have received a copy of the GNU General Public License # along with this program. If not, see https://www.gnu.org/licenses/. -AC_INIT([GNU nano], [8.3], [nano-devel@gnu.org], [nano]) +AC_INIT([GNU nano], [8.4], [nano-devel@gnu.org], [nano]) AC_CONFIG_SRCDIR([src/nano.c]) AC_CANONICAL_HOST AM_INIT_AUTOMAKE([1.14]) diff --git a/doc/faq.html b/doc/faq.html @@ -92,7 +92,7 @@ <h3 id="1.3">1.3. Why the name change from TIP?</h3> <blockquote><p>On January 10, 2000, TIP was officially renamed to nano because of a namespace conflict with another program called 'tip'. The original 'tip' program &quot;establishes a full duplex terminal connection to a remote host&quot;, and was included with many older Unix systems (and newer ones like Solaris). The conflict was not noticed at first because there is no 'tip' utility included with most GNU/Linux distributions (where nano was developed).</p></blockquote> <h3 id="1.4">1.4. What is the current version of nano?</h3> -<blockquote><p>The current version of nano <i>should</i> be <b>8.3</b>. Of course, you should always check the <a href="https://nano-editor.org/">nano homepage</a> to see what the latest and greatest version is.</p></blockquote> +<blockquote><p>The current version of nano <i>should</i> be <b>8.4</b>. Of course, you should always check the <a href="https://nano-editor.org/">nano homepage</a> to see what the latest and greatest version is.</p></blockquote> <h3 id="1.5">1.5. I want to read the man page without having to download the program!</h3> <blockquote><p>Jeez, demanding, aren't we? Okay, look <a href="https://nano-editor.org/dist/latest/nano.1.html">here</a>.</p></blockquote> <hr width="100%"> diff --git a/doc/nano.1 b/doc/nano.1 @@ -16,7 +16,7 @@ .\" Documentation License along with this program. If not, see .\" <https://www.gnu.org/licenses/>. .\" -.TH NANO 1 "version 8.3" "December 2024" +.TH NANO 1 "version 8.4" "April 2025" .SH NAME nano \- Nano's ANOther text editor, inspired by Pico diff --git a/doc/nano.texi b/doc/nano.texi @@ -13,8 +13,8 @@ The complete manual for the GNU nano text editor. @smallbook @set EDITION 0.8 -@set VERSION 8.3 -@set UPDATED December 2024 +@set VERSION 8.4 +@set UPDATED April 2025 @dircategory Editors @direntry @@ -29,7 +29,7 @@ The complete manual for the GNU nano text editor. @title GNU @command{nano} @subtitle a small and friendly text editor -@subtitle version 8.3 +@subtitle version 8.4 @author Chris Allegretta @@ -79,7 +79,7 @@ For suggesting improvements: @email{nano-devel@@gnu.org} @node Top @top -This manual documents GNU @command{nano}, version 8.3. +This manual documents GNU @command{nano}, version 8.4. @menu * Introduction:: diff --git a/doc/nanorc.5 b/doc/nanorc.5 @@ -16,7 +16,7 @@ .\" Documentation License along with this program. If not, see .\" <https://www.gnu.org/licenses/>. .\" -.TH NANORC 5 "version 8.3" "December 2024" +.TH NANORC 5 "version 8.4" "April 2025" .SH NAME nanorc \- GNU nano's configuration file diff --git a/doc/rnano.1 b/doc/rnano.1 @@ -16,7 +16,7 @@ .\" Documentation License along with this program. If not, see .\" <https://www.gnu.org/licenses/>. .\" -.TH RNANO 1 "version 8.3" "December 2024" +.TH RNANO 1 "version 8.4" "April 2025" .SH NAME rnano \- a restricted nano diff --git a/roll-a-release.sh b/roll-a-release.sh @@ -1,6 +1,6 @@ #!/bin/bash -VERSION="8.3" +VERSION="8.4" ./configure -C --enable-tiny && make && ./configure -C &&