From: Gregory Heytings <gregory@heytings.org>
To: Vincent Lefevre <vincent@vinc17.net>
Cc: Eli Zaretskii <eliz@gnu.org>, 58992@debbugs.gnu.org
Subject: bug#58992: 28.2; "lax space matching" no longer works
Date: Thu, 03 Nov 2022 18:43:10 +0000 [thread overview]
Message-ID: <64a257e7178dabe04cb2@heytings.org> (raw)
In-Reply-To: <20221103182809.GG9807@zira.vinc17.org>
>> commit 74d091a0a665da5dc01989d1b06a61ee21b975b2
>> Author: Lars Ingebrigtsen <larsi@gnus.org>
>> Date: Fri Sep 10 12:27:28 2021 +0200
>>
>> Change the default value of search-whitespace-regexp
>>
>> * lisp/isearch.el (search-whitespace-regexp): Change the default
>> to always exclude newlines from the set (bug#21278). It used to
>> be mode-dependent whether newlines were included or not, and this
>> was confusing as a user interface.
>>
>> which changed the default value of search-whitespace-regexp from
>> "\\s-+" to "[ \t]".
>
> This is still buggy in Emacs 28.2 if I change the value:
>
> This works in Fundamental mode, but not in Lisp mode.
>
As the commit message explains, "It used to be mode-dependent whether
newlines were included or not, and this was confusing as a user
interface." Hence your confusion. You will see the same in Emacs 27 and
28: RET is space in fundamental mode and not space in text mode.
>
> BTW, I don't understand what "\\s-+" means.
>
It means "match any character whose syntax is "space".
next prev parent reply other threads:[~2022-11-03 18:43 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 16:53 bug#58992: 28.2; "lax space matching" no longer works Vincent Lefevre
2022-11-03 17:04 ` Eli Zaretskii
2022-11-03 17:21 ` Vincent Lefevre
2022-11-03 17:34 ` Vincent Lefevre
2022-11-03 18:05 ` Eli Zaretskii
2022-11-03 17:49 ` Gregory Heytings
2022-11-03 17:56 ` Vincent Lefevre
2022-11-03 18:02 ` Vincent Lefevre
2022-11-03 18:04 ` Gregory Heytings
2022-11-03 18:04 ` Vincent Lefevre
2022-11-03 18:11 ` Gregory Heytings
2022-11-03 18:18 ` Gregory Heytings
2022-11-03 18:28 ` Vincent Lefevre
2022-11-03 18:39 ` Eli Zaretskii
2022-11-03 18:43 ` Gregory Heytings [this message]
2022-11-03 18:36 ` Juri Linkov
2022-11-03 18:18 ` Eli Zaretskii
2022-11-03 18:02 ` Gregory Heytings
2022-11-03 18:03 ` Eli Zaretskii
2022-11-03 18:33 ` Vincent Lefevre
2022-11-03 18:42 ` Eli Zaretskii
2022-11-03 18:52 ` Vincent Lefevre
2022-11-03 19:22 ` Eli Zaretskii
2022-11-04 2:29 ` Vincent Lefevre
2022-11-04 3:38 ` Vincent Lefevre
2022-11-04 7:25 ` Eli Zaretskii
2022-11-04 10:46 ` Vincent Lefevre
2022-11-04 11:50 ` Eli Zaretskii
2022-11-04 7:14 ` Eli Zaretskii
2022-11-04 10:41 ` Vincent Lefevre
2022-11-04 10:56 ` Vincent Lefevre
2022-11-04 11:52 ` Eli Zaretskii
2022-11-04 13:04 ` Vincent Lefevre
2022-11-04 13:40 ` Eli Zaretskii
2022-11-04 11:48 ` Eli Zaretskii
2022-11-04 3:30 ` Vincent Lefevre
2022-11-04 7:21 ` Eli Zaretskii
2022-11-04 10:15 ` Vincent Lefevre
2022-11-04 11:38 ` Andreas Schwab
2022-11-04 12:47 ` Vincent Lefevre
2022-11-04 13:25 ` Andreas Schwab
2022-11-04 14:32 ` Vincent Lefevre
2022-11-04 14:35 ` Andreas Schwab
2022-11-04 15:02 ` Vincent Lefevre
2022-11-04 15:24 ` Andreas Schwab
2022-11-04 11:45 ` Eli Zaretskii
2022-11-04 13:56 ` Robert Pluim
2022-11-04 14:04 ` Eli Zaretskii
2022-11-04 15:00 ` Vincent Lefevre
2022-11-04 15:23 ` Eli Zaretskii
2022-11-05 1:55 ` Vincent Lefevre
2022-11-05 6:47 ` Eli Zaretskii
2022-11-05 11:20 ` Vincent Lefevre
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=64a257e7178dabe04cb2@heytings.org \
--to=gregory@heytings.org \
--cc=58992@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=vincent@vinc17.net \
/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).