GNU bug report logs - #58992
28.2; "lax space matching" no longer works

Previous Next

Full log

Message #160 received at 58992 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Vincent Lefevre <vincent <at> vinc17.net>
Cc: rpluim <at> gmail.com, 58992 <at> debbugs.gnu.org
Subject: Re: bug#58992: 28.2; "lax space matching" no longer works
Date: Sat, 05 Nov 2022 08:47:27 +0200

> Date: Sat, 5 Nov 2022 02:55:54 +0100
> From: Vincent Lefevre <vincent <at> vinc17.net>
> Cc: rpluim <at> gmail.com, 58992 <at> debbugs.gnu.org
> 
> On 2022-11-04 17:23:11 +0200, Eli Zaretskii wrote:
> > > Date: Fri, 4 Nov 2022 16:00:02 +0100
> > > From: Vincent Lefevre <vincent <at> vinc17.net>
> > > Cc: Robert Pluim <rpluim <at> gmail.com>, 58992 <at> debbugs.gnu.org
> > > 
> > > IMHO, Section "Syntax of Regular Expressions" (for both Emacs and Elisp)
> > > should warn that the meaning of a regular expression may depend on the
> > > major mode.
> > 
> > Already done.  Did you look at the latest version in Git?
> 
> If I'm not mistaken, it is said only in Section "Character Classes",
> not at a higher level.

Yes, because that's where [:space:] is described.  Saying it in other
places would be a didactic mistake, because those other places are not
directly related to use of character classes in regular expressions.

In general, when one looks for details of some Emacs feature, one has
to read the parts of the manual which actually describe that feature
in all its details.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.