From: Eli Zaretskii <eliz@gnu.org>
To: Vincent Lefevre <vincent@vinc17.net>
Cc: 58992@debbugs.gnu.org
Subject: bug#58992: 28.2; "lax space matching" no longer works
Date: Fri, 04 Nov 2022 09:14:57 +0200 [thread overview]
Message-ID: <83wn8b5gy6.fsf@gnu.org> (raw)
In-Reply-To: <20221104022950.GJ9807@zira.vinc17.org> (message from Vincent Lefevre on Fri, 4 Nov 2022 03:29:50 +0100)
> Date: Fri, 4 Nov 2022 03:29:50 +0100
> From: Vincent Lefevre <vincent@vinc17.net>
> Cc: 58992@debbugs.gnu.org
>
> > Because the newline's syntax is not "whitespace" in those modes.
>
> OK, but then, the question is why the newline's syntax is not
> "whitespace" in those modes...
Because the mode sets up its syntax tables for various needs, none of
which is Isearch.
> > > In C, except for the preprocessor, a newline is similar to a space
> > > character.
> >
> > The syntax we give to each character in a major mode depends on what
> > the mode needs to do with that character. For example, a mode might
> > have a good reason to give the newline the '>' syntax, because the
> > newline ends a comment in those modes.
>
> In C, the conventional comment is /* ... */ and the newline does not
> end a comment. In any case, /* ... */ is more practical to write
> multi-line comments in C (no need to repeat comment starters at the
> beginning of every line), and if one wants to search in comments,
> the newline should be regarded as a whitespace.
This is not really relevant. Major modes set up their syntax tables
as they consider relevant, and we won't change that for the benefit of
search-whitespace-regexp. The lesson to learn here is not to base
Isearch-related regexps on character syntax, because that changes its
meaning with the major mode, something many users will not expect.
> > > BTW, it actually doesn't match either for the Texinfo mode, and
> > > I don't see any reason why.
> >
> > In which version of Emacs, and with what value of
> > search-whitespace-regexp?
>
> Both 27.1 and 28.2 (Debian for both), with search-whitespace-regexp
> set to "\\s-+".
Then don't use "\\s-+". The manual suggests a different regexp for
your preference, and it does so for a good reason. Why are you using
a regexp that we already concluded to be problematic and stopped
using? You will get yourself in the same problems we decided to
avoid.
next prev parent reply other threads:[~2022-11-04 7:14 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
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 [this message]
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=83wn8b5gy6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58992@debbugs.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).