GNU bug report logs - #22494
still can't search for two spaces

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: John Wiegley <johnw <at> gnu.org>
Cc: 22494 <at> debbugs.gnu.org, mbork <at> mbork.pl, rms <at> gnu.org, drew.adams <at> oracle.com,
 jidanni <at> jidanni.org
Subject: Re: bug#22494: still can't search for two spaces
Date: Wed, 03 Feb 2016 17:28:11 +0200

> From: John Wiegley <jwiegley <at> gmail.com>
> Date: Tue, 02 Feb 2016 22:45:41 -0800
> Cc: 22494 <at> debbugs.gnu.org, mbork <at> mbork.pl, rms <at> gnu.org, jidanni <at> jidanni.org
> 
> If the user types something into the search string, and exactly that something
> is present in the buffer, Emacs should locate it before any "lax" variant.

Of course, with the way it works in Emacs, there's no "before".
There's either this or that: either Emacs finds only the literal
matches, or it finds both literal and lax matches.  If the latter, the
first literal or lax match after point will be the first one found,
even if it's a lax match and there's a literal match farther away.

Previous Next

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