GNU bug report logs - #1800
23.0.60; Changed meaning of * in buffer name completion

Previous Next

Package: emacs;

Reported by: rms <at> gnu.org

Date: Tue, 6 Jan 2009 12:40:05 UTC

Severity: normal

Done: Chong Yidong <cyd <at> stupidchicken.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Juri Linkov <juri <at> jurta.org>
To: Stefan Monnier <monnier <at> IRO.UMontreal.CA>
Cc: 1800 <at> debbugs.gnu.org, rms <at> gnu.org, emacs-pretest-bug <at> gnu.org
Subject: bug#1800: 23.0.60; Changed meaning of * in buffer name completion
Date: Wed, 07 Jan 2009 00:54:17 +0200
>> Trying to switch to a killed buffer that had `*' at the beginning
>> of its name (e.g. *grep*) typing `* g TAB' displays a large list
>> of irrelevant buffer names.
> [...]
>>   [No match, type TAB again for * as a wildcard]
>
> Here's another option: only treat * as a wildcard if it doesn't match
> anything existing.  I.e. if you have buffers that start with "*", then
> "*g" will not treat the * as a wildcard.  To force the use of
> a wildcard, we could let the user type "**g".

It seems unlikely not to have a buffer that starts with "*".
There are always such buffers as *scratch*, *Messages*, *Completions*.
OTOH, "**g" will help, but it has the same drawback as using "\*g"
for a literal character *, i.e. it is not as obvious as using a single *.

-- 
Juri Linkov
http://www.jurta.org/emacs/




This bug report was last modified 15 years and 288 days ago.

Previous Next


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