[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#58992: 28.2; "lax space matching" no longer works
From: |
Vincent Lefevre |
Subject: |
bug#58992: 28.2; "lax space matching" no longer works |
Date: |
Fri, 4 Nov 2022 11:56:37 +0100 |
User-agent: |
Mutt/2.2.7+51 (a318ca5a) vl-149028 (2022-10-21) |
On 2022-11-04 11:41:15 +0100, Vincent Lefevre wrote:
> On 2022-11-04 09:14:57 +0200, Eli Zaretskii wrote:
> > > 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.
>
> But the manual does not discourage the use of syntax classes
> for searching, and it is not clear from the description that
> they won't do what the user expects.
I've searched on the web and found the Emacs wiki
https://www.emacswiki.org/emacs/RegularExpression
It even encourages the use of "\s-" for searching: this is a page
mainly for searching (see the first line of the text), and in the
"Regexp Syntax Basics" (note: *basics*):
\sc character with c syntax (e.g. \s- for whitespace char)
So users are very likely to use it.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
- bug#58992: 28.2; "lax space matching" no longer works, (continued)
- bug#58992: 28.2; "lax space matching" no longer works, Eli Zaretskii, 2022/11/03
- bug#58992: 28.2; "lax space matching" no longer works, Vincent Lefevre, 2022/11/03
- bug#58992: 28.2; "lax space matching" no longer works, Eli Zaretskii, 2022/11/03
- bug#58992: 28.2; "lax space matching" no longer works, Vincent Lefevre, 2022/11/03
- bug#58992: 28.2; "lax space matching" no longer works, Vincent Lefevre, 2022/11/03
- bug#58992: 28.2; "lax space matching" no longer works, Eli Zaretskii, 2022/11/04
- bug#58992: 28.2; "lax space matching" no longer works, Vincent Lefevre, 2022/11/04
- bug#58992: 28.2; "lax space matching" no longer works, Eli Zaretskii, 2022/11/04
- bug#58992: 28.2; "lax space matching" no longer works, Eli Zaretskii, 2022/11/04
- bug#58992: 28.2; "lax space matching" no longer works, Vincent Lefevre, 2022/11/04
- bug#58992: 28.2; "lax space matching" no longer works,
Vincent Lefevre <=
- bug#58992: 28.2; "lax space matching" no longer works, Eli Zaretskii, 2022/11/04
- bug#58992: 28.2; "lax space matching" no longer works, Vincent Lefevre, 2022/11/04
- bug#58992: 28.2; "lax space matching" no longer works, Eli Zaretskii, 2022/11/04
- bug#58992: 28.2; "lax space matching" no longer works, Eli Zaretskii, 2022/11/04
- bug#58992: 28.2; "lax space matching" no longer works, Vincent Lefevre, 2022/11/03
- bug#58992: 28.2; "lax space matching" no longer works, Eli Zaretskii, 2022/11/04
- bug#58992: 28.2; "lax space matching" no longer works, Vincent Lefevre, 2022/11/04
- bug#58992: 28.2; "lax space matching" no longer works, Andreas Schwab, 2022/11/04
- bug#58992: 28.2; "lax space matching" no longer works, Vincent Lefevre, 2022/11/04
- bug#58992: 28.2; "lax space matching" no longer works, Andreas Schwab, 2022/11/04