From: "Drew Adams" <drew.adams@oracle.com>
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: Wed, 7 Jan 2009 10:05:17 -0800 [thread overview]
Message-ID: <004001c970f2$810f7440$c2b22382@us.oracle.com> (raw)
In-Reply-To: <87mye3t5hz.fsf@jurta.org>
> > This is not (necessarily) about partial completion. The new
> > feature is that a list of completion methods is used, in
> > order, to try to complete user input. That list is the
> > value of `completion-styles', which by default is `(basic
> > partial-completion)'.
>
> I think we should replace `partial-completion' in the default
> value of `completion-styles' with a new completion method, e.g.
> `confirm-partial-completion'.
Providing `confirm-partial-completion' as another alternative completion style
is fine, but why make it the default behavior? What's wrong with the traditional
behavior as default?
next prev parent reply other threads:[~2009-01-07 18:05 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 [this message]
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
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='004001c970f2$810f7440$c2b22382@us.oracle.com' \
--to=drew.adams@oracle.com \
--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 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).