From: Juri Linkov <juri@linkov.net>
To: 21278@debbugs.gnu.org
Cc: larsi@gnus.org, rms@gnu.org, bruce.connor.am@gmail.com,
monnier@iro.umontreal.ca
Subject: bug#21278: char-fold isearch: space and newline still broken
Date: Thu, 09 Sep 2021 20:32:53 +0300 [thread overview]
Message-ID: <87ee9xu2tm.fsf@mail.linkov.net> (raw)
In-Reply-To: <jwvo89436q5.fsf-monnier+emacs@gnu.org> (Stefan Monnier via's message of "Tue, 07 Sep 2021 08:36:39 -0400")
>> Building such mode-independent features on syntax properties
>> is IME asking for trouble.
>> Stefan, WDYT?
>
> Agreed. I'd use something like [ \t] or [ \t\n] or even [\0-\s].
Seconded. Everyone who wants to match a newline,
still needs to customize search-whitespace-regexp
to include \n, e.g. "\\(?:\\s-\\|\n\\)+", so an explicit
list of characters would be more deterministic.
next prev parent reply other threads:[~2021-09-09 17:32 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ee9xu2tm.fsf@mail.linkov.net \
--to=juri@linkov.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.