[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:15:13 +0100 |
User-agent: |
Mutt/2.2.7+51 (a318ca5a) vl-149028 (2022-10-21) |
On 2022-11-04 09:21:04 +0200, Eli Zaretskii wrote:
> > Date: Fri, 4 Nov 2022 04:30:38 +0100
> > From: Vincent Lefevre <vincent@vinc17.net>
> > Cc: 58992@debbugs.gnu.org
> >
> > The [[:space:]\n]+ in the doc is misleading. Since a newline character
> > is a whitespace, [[:space:]]+ is sufficient.
>
> That is only true in major modes where the newline has the
> "whitespace" syntax, see the description of [:space:] in the ELisp
> manual. I guess you tried this in Fundamental mode or somesuch?
Wow! This is really confusing! [:space:] is defined by POSIX, and the
manual even refers to it:
A character alternative can also specify named character classes
(*note Char Classes::). This is a POSIX feature. [...]
You must not change its behavior! Making it depend on the major mode
is even worse.
If the intent is to have a different meaning, a different name should
be chosen, such as [:whitespace:] (though I'm not sure whether some
names are reserved by POSIX).
--
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/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, 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, 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 <=
- 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
- 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
- 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, Robert Pluim, 2022/11/04
- bug#58992: 28.2; "lax space matching" no longer works, Eli Zaretskii, 2022/11/04