[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
David Lawrence Ramsey
Wed, 7 Jan 2004 14:13:59 -0800 (PST)
There's one remaining bug in the replace routine. It turns out that
regexes involving "*" as well as "^" and/or "$" can lead to multiple
replacements on the same line: one with a length of however many matches
of the "*" part there are, and one of zero length. (For example, try
replacing "^( )*" on lines beginning with at least one space.) To fix
this, I've made one last change: all regexes containing "^" and/or "$",
and not just the zero-length ones, are now only found once per line.
Instead of setting the relevant flag (now bol_eol instead of
caretdollar, since the former is a bit clearer) when match_len is 0, it
now calls regexec() with the already-found string and REG_NOTBOL and
It turns out that the same problem affects normal searching (in both
1.3.x and 1.2.x): when searching for the above puts you on the
magicline, nano will say that the occurrence at the magicline is the
only occurrence and not move anymore. However, seeing as this doesn't
cause infinite loops, it's been long enough since 1.3.0, and current CVS
contains a lot of fixes for other things, I'm postponing it until after
1.3.1 is released. It should be easy to fix, anyway.
Aside from that change, there have only been a few cosmetic changes:
since I got no feedback on the FAQ entry and it's needed to explain
verbatim input to the uninitiated, it's now in CVS (after I ran it by my
sister who hasn't used nano, and she thought it was clear enough); the
NEWS file has been reformatted to have 72 characters per line and has a
few typo fixes in it; the manpages now include version numbers, as the
info page already does; and one set of comments in
get_escape_seq_kbinput() have been updated to document the escape
sequences for Shift-Left and Shift-Right on Eterm.
Sluggy.Net: The Sluggy Freelance Community!
- [Nano-devel] updates,
David Lawrence Ramsey <=