From: "Drew Adams" <drew.adams@oracle.com>
To: <rms@gnu.org>, <1757@emacsbugs.donarmstrong.com>,
<emacs-pretest-bug@gnu.org>
Subject: bug#1757: 23.0.60; completion DWIM too clever
Date: Thu, 1 Jan 2009 09:59:45 -0800 [thread overview]
Message-ID: <007601c96c3a$bba3d8b0$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <E1LIPn1-0001tj-1R@fencepost.gnu.org>
> I typed C-x b *d TAB and it offered me as completions `diary'
> and `old', neither of which starts with a `*'.
>
> I typed C-x b *di TAB and it completed to `diary', which is not
> even a completion of what I typed.
>
> It is extremely annoying to discard the user's input characters.
I couldn't agree more. The is (the formerly optional) partial completion at
work. It is now the default behavior to first try the traditional completion,
and if that finds no matches, automatically try partial completion. IMO, the
default behavior should remain as it was in Emacs 22 (21, 20...), and the new
behavior should be optional.
With the traditional behavior, if there are no buffers with prefix `*', you are
told so immediately: [No match]. With the new, partial-completion behavior, you
are given possible completions that do not complete `*' in the normal way (as a
literal prefix).
To get the traditional behavior, you now need to customize option
`completion-styles', to be `(basic)', not `(basic partial-completion)'. This
significant change was made with no discussion, AFAIK.
See bug #1512:
http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=1512
next prev parent reply other threads:[~2009-01-01 17:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-01 15:48 bug#1757: 23.0.60; completion DWIM too clever Richard M Stallman
2009-01-01 17:59 ` Drew Adams [this message]
2009-01-01 18:26 ` Lennart Borgman
2009-01-01 19:10 ` Drew Adams
2009-01-02 17:14 ` Richard M Stallman
2011-09-11 22:10 ` Drew Adams
2011-09-11 22:16 ` Lars Magne Ingebrigtsen
2009-01-02 17:14 ` Richard M Stallman
2009-01-05 22:19 ` Stefan Monnier
2009-01-05 22:25 ` Processed: " Emacs bug Tracking System
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='007601c96c3a$bba3d8b0$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=1757@emacsbugs.donarmstrong.com \
--cc=emacs-pretest-bug@gnu.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).