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

Previous Next

Package: emacs;

Reported by: Vincent Lefevre <vincent <at> vinc17.net>

Date: Thu, 3 Nov 2022 16:54:02 UTC

Severity: normal

Found in version 28.2

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Vincent Lefevre <vincent <at> vinc17.net>
Cc: 58992 <at> debbugs.gnu.org
Subject: bug#58992: 28.2; "lax space matching" no longer works
Date: Thu, 03 Nov 2022 20:05:28 +0200
> Date: Thu, 3 Nov 2022 18:34:18 +0100
> From: Vincent Lefevre <vincent <at> vinc17.net>
> Cc: 58992 <at> debbugs.gnu.org
> 
> > I tested with "emacs -Q", and I've just tested again. I confirm the
> > behavior I could see: a newline character is matched. That's Debian's
> > package emacs-gtk 1:27.1+1-3.1+b1. So perhaps Debian has changed the
> > default (but no changes were announced in Debian for Emacs 28, whose
> > behavior is different).
> 
> In the officiel lisp/isearch.el file from the Debian/stable package
> (i.e. *not* in the debian subdirectory):
> 
> (defcustom search-whitespace-regexp (purecopy "\\s-+")
> 
> So it doesn't seem to be a Debian customization.

OK, thanks for solving this mystery.




This bug report was last modified 2 years and 203 days ago.

Previous Next


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