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

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: rms <at> gnu.org, Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 21278 <at> debbugs.gnu.org, larsi <at> gnus.org, bruce.connor.am <at> gmail.com
Subject: bug#21278: char-fold isearch: space and newline still broken
Date: Tue, 07 Sep 2021 09:19:53 +0300

> From: Richard Stallman <rms <at> gnu.org>
> Cc: larsi <at> gnus.org, 21278 <at> debbugs.gnu.org, bruce.connor.am <at> gmail.com
> Date: Mon, 06 Sep 2021 23:17:45 -0400
> 
>   > I think that's because in Mail mode we have:
> 
>   >   (char-syntax ?\n) => 32 ; SPC
> 
>   > whereas in *scratch*:
> 
>   >   (char-syntax ?\n) => 62 ; >
> 
>   > And the regexp in search-whitespace-regexp is "\\s-+".
> 
> That seems plausible.
> 
> I still say it is a bug.  Incremental search should not equate
> newline with spaces, at least not by default.  It is right to
> treat newline as whitespace in other commands, but not in search.
> 
> What would be a good fix?  Change the syntax of newline?
> What would be a good choice?

No, I think we should leave the syntax of the newline alone, I bet too
much depends on it.

I think we should change the default value of search-whitespace-regexp
instead.  Building such mode-independent features on syntax properties
is IME asking for trouble.

Stefan, WDYT?

Previous Next

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