nano

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

commit 0e963be59d66ed2f0f58ea33d251f8cc7b173d9c
parent b5a7bbf4f339cdd939a14b994a2bf02e9b64e26c
Author: David Lawrence Ramsey <pooka109@gmail.com>
Date:   Mon,  5 Jun 2006 15:44:55 +0000

mention the removal of the workaround for glibc 2.2.3's broken regexec()
in UPGRADE too


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3625 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

Diffstat:
MChangeLog | 2+-
MUPGRADE | 4++++
2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/ChangeLog b/ChangeLog @@ -142,7 +142,7 @@ CVS code - replace it with a FAQ entry explaining the problem, since it could break anything using extended regular expressions, and glibc 2.2.3 is old. Changes to configure.ac, faq.html, - nano.h, and proto.h; removal of safe_regexec(). (DLR) + nano.h, proto.h, and UPGRADE; removal of safe_regexec(). (DLR) - browser.c: do_browser() - Reference NANO_GOTODIR_(ALT|F)?KEY instead of diff --git a/UPGRADE b/UPGRADE @@ -48,6 +48,10 @@ Visible changes since 1.2 - Many more functions available at the statusbar prompt: moving to the next or previous word, searching for matching brackets, "Verbatim Input" mode, etc. + - The glibc 2.2.3 crashes involving extended regular expressions are + no longer worked around, as they can break anything using extended + regular expressions, and glibc 2.2.3 is old. You should upgrade to + at least glibc 2.2.4. * File Handling - Automatic adding of newlines to the ends of files without them can