From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21278@debbugs.gnu.org, juri@linkov.net, monnier@iro.umontreal.ca,
bruce.connor.am@gmail.com, rms@gnu.org
Subject: bug#21278: char-fold isearch: space and newline still broken
Date: Fri, 10 Sep 2021 12:57:09 +0200 [thread overview]
Message-ID: <87y284puka.fsf@gnus.org> (raw)
In-Reply-To: <83tuisitux.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 10 Sep 2021 13:54:14 +0300")
Eli Zaretskii <eliz@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...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-09-10 10:57 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
2021-09-10 10:28 ` Lars Ingebrigtsen
2021-09-10 10:54 ` Eli Zaretskii
2021-09-10 10:57 ` Lars Ingebrigtsen [this message]
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=87y284puka.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=21278@debbugs.gnu.org \
--cc=bruce.connor.am@gmail.com \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--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).