From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Juri Linkov <juri@jurta.org>
Cc: emacs-pretest-bug@gnu.org, rms@gnu.org, 1800@emacsbugs.donarmstrong.com
Subject: bug#1800: 23.0.60; Changed meaning of * in buffer name completion
Date: Tue, 06 Jan 2009 17:14:10 -0500 [thread overview]
Message-ID: <jwv63kskrv4.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <87r63gs1il.fsf@jurta.org> (Juri Linkov's message of "Tue, 06 Jan 2009 21:00:34 +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".
Stefan
next prev parent reply other threads:[~2009-01-06 22:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87skfslnlx.fsf@cyd.mit.edu>
2009-01-06 12:31 ` bug#1800: 23.0.60; Changed meaning of * in buffer name completion Richard M Stallman
2009-01-06 19:00 ` Juri Linkov
2009-01-06 22:14 ` Stefan Monnier [this message]
2009-01-06 22:54 ` Juri Linkov
2009-01-07 5:35 ` Drew Adams
2009-01-07 20:09 ` Richard M Stallman
2009-01-06 22:36 ` Drew Adams
2009-01-06 23:12 ` Juri Linkov
2009-01-07 5:35 ` Drew Adams
2009-01-07 12:07 ` Juri Linkov
2009-01-07 15:56 ` Drew Adams
2009-01-07 16:48 ` Drew Adams
2009-01-07 17:43 ` Juri Linkov
2009-01-07 18:05 ` Drew Adams
2009-01-07 19:30 ` Juri Linkov
2009-01-06 22:59 ` Richard M Stallman
2009-08-15 22:35 ` bug#1800: marked as done (23.0.60; Changed meaning of * in buffer name completion) Emacs bug Tracking System
2009-03-09 21:25 bug#1800: 23.0.60; Changed meaning of * in buffer name completion Xavier Maillard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv63kskrv4.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=1800@emacsbugs.donarmstrong.com \
--cc=emacs-pretest-bug@gnu.org \
--cc=juri@jurta.org \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.