From: Richard M Stallman <rms@gnu.org>
To: Juri Linkov <juri@jurta.org>, 1800@emacsbugs.donarmstrong.com
Cc: emacs-pretest-bug@gnu.org, bug-gnu-emacs@gnu.org,
bug-submit-list@donarmstrong.com,
1800@emacsbugs.donarmstrong.com
Subject: bug#1800: 23.0.60; Changed meaning of * in buffer name completion
Date: Tue, 06 Jan 2009 17:59:44 -0500 [thread overview]
Message-ID: <E1LKKtk-0008FG-Jp@fencepost.gnu.org> (raw)
In-Reply-To: <87r63gs1il.fsf@jurta.org> (message from Juri Linkov on Tue, 06 Jan 2009 21:00:34 +0200)
A better variant is to provide two-step completion. So when there is
no buffer matching `*g' literally then display a message like
[No match, type TAB again for * as a wildcard]
That is a good idea. It would provide the same benefit of the
existing feature, but without the inconvenience.
next prev parent reply other threads:[~2009-01-06 22:59 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1LKKtk-0008FG-Jp@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=1800@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=bug-submit-list@donarmstrong.com \
--cc=emacs-pretest-bug@gnu.org \
--cc=juri@jurta.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).