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

Previous Next

Full log

Message #112 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: 58992 <at> debbugs.gnu.org
Subject: Re: bug#58992: 28.2; "lax space matching" no longer works
Date: Fri, 04 Nov 2022 13:48:01 +0200

> Date: Fri, 4 Nov 2022 11:41:15 +0100
> From: Vincent Lefevre <vincent <at> vinc17.net>
> Cc: 58992 <at> debbugs.gnu.org
> 
> On 2022-11-04 09:14:57 +0200, Eli Zaretskii wrote:
> > > Date: Fri, 4 Nov 2022 03:29:50 +0100
> > > From: Vincent Lefevre <vincent <at> vinc17.net>
> > > Cc: 58992 <at> 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.

It depends on the expectations of the user.  The manual does document
which classes mean what, and the user then should decide whether it
fits the particular job.

Previous Next

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