GNU bug report logs - #21278
char-fold isearch: space and newline

Previous Next

Full log

View this message in rfc822 format

From: Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
To: Augusto Stoffel <arstoffel <at> gmail.com>
Cc: 21278 <at> debbugs.gnu.org, rms <at> gnu.org, bruce.connor.am <at> gmail.com, juri <at> linkov.net, monnier <at> iro.umontreal.ca, Lars Ingebrigtsen <larsi <at> gnus.org>
Subject: bug#21278: char-fold isearch: space and newline still broken
Date: Fri, 10 Sep 2021 15:17:19 +0200

Augusto Stoffel <arstoffel <at> gmail.com> writes:

> On Fri, 10 Sep 2021 at 12:57, Lars Ingebrigtsen <larsi <at> gnus.org> wrote:
>
>> Eli Zaretskii <eliz <at> gnu.org> writes:
>>
>>>> It seems like everybody agrees that the old value was confusing, so I've
>>>> now changed it to [ \t] in Emacs 28.
>>>
>>> Shouldn't it be [ \t]+ instead?
>>
>> Oops.  Looks like I'm going for the "most errors in a trivial one-line
>> patch" record here...
>
> For the record, search-whitespace-regexp could have more useful values
> suggested in customize.  I can think of:
>
> - not too lax: "[ \\t]+"
> - match across lines: "[ \\t\\n]+"
> - eat punctuation: "\\W+"
> - fuzzy: ".*?"

Seconded.  I expect this to be a common customization: when searching
for compound expressions ("regular expression", "environment variable"…)
through prose filled using hard newlines (manpages, info nodes,
docstrings…), I have always found it useful for isearch to treat
newlines as regular whitespace.

If isearch no longer behaves like that by default, I'm sure users would
at least appreciate Customize suggesting some ready-made values.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.