From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 21278@debbugs.gnu.org, larsi@gnus.org, bruce.connor.am@gmail.com
Subject: bug#21278: char-fold isearch: space and newline still broken
Date: Tue, 07 Sep 2021 09:19:53 +0300 [thread overview]
Message-ID: <83sfygq54m.fsf@gnu.org> (raw)
In-Reply-To: <E1mNRcH-0007HM-T4@fencepost.gnu.org> (message from Richard Stallman on Mon, 06 Sep 2021 23:17:45 -0400)
> From: Richard Stallman <rms@gnu.org>
> Cc: larsi@gnus.org, 21278@debbugs.gnu.org, bruce.connor.am@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?
next prev parent reply other threads:[~2021-09-07 6:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 5:04 bug#21278: 25.0.50; char-fold search is a screw, and I can't see how to disable Richard Stallman
2015-08-18 21:48 ` Artur Malabarba
2015-08-19 22:20 ` Juri Linkov
2015-08-19 22:59 ` Artur Malabarba
2021-09-04 7:04 ` bug#21278: char-fold isearch: space and newline Lars Ingebrigtsen
2021-09-06 3:09 ` bug#21278: char-fold isearch: space and newline still broken Richard Stallman
2021-09-06 5:59 ` Eli Zaretskii
2021-09-07 3:17 ` Richard Stallman
2021-09-07 6:19 ` Eli Zaretskii [this message]
2021-09-07 12:36 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-09 17:32 ` Juri Linkov
2021-09-10 10:28 ` Lars Ingebrigtsen
2021-09-10 10:54 ` Eli Zaretskii
2021-09-10 10:57 ` Lars Ingebrigtsen
2021-09-10 11:56 ` Augusto Stoffel
2021-09-10 13:17 ` Kévin Le Gouguec
2021-09-11 12:12 ` Lars Ingebrigtsen
2021-09-11 12:52 ` Augusto Stoffel
2021-09-13 7:26 ` Lars Ingebrigtsen
2021-09-06 8:32 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83sfygq54m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21278@debbugs.gnu.org \
--cc=bruce.connor.am@gmail.com \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).