From: James Cloos <cloos@jhcloos.com>
To: ding@gnus.org
Cc: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: bug#499: 23.0.60; minibuffer tab completion regression
Date: Sun, 29 Jun 2008 11:06:50 -0400 [thread overview]
Message-ID: <m3vdzs46vy.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <jwv63rsh2c6.fsf-monnier+emacsbugreports@gnu.org> (Stefan Monnier's message of "Sun, 29 Jun 2008 08:15:41 -0400")
>>>>> "Stefan" == Stefan Monnier <monnier@iro.umontreal.ca> writes:
For ding readers:
gnus-article-save-part's setup of appending the proposed filename to the
current save dir as the prompt no longer allows one to easily type in a
new path using tab completion without customizing completion-styles as
Stefan describes below.
JimC> In short, pathname tab completion used to ignore everything at
JimC> and right of point whereas now it does not.
Stefan> Indeed, it does now: it constrains the list of possible
Stefan> completions to those that include the text after point.
Stefan> E.g. if your minibuffer is "/foo/bat.c" you can place point
Stefan> after "bat" and hit TAB to complete to a filename among
Stefan> "bat*.c".
Stefan> You can get the old behavior with one of the following:
Stefan> - C-k TAB C-y
Stefan> - customizing completion-styles: you can for example replace
Stefan> `basic' by `emacs22' to get back Emacs-22's behavior. Note
Stefan> that if you select `emacs21' you won't get this behavior
Stefan> since Emacs-21 (and all previous Emacs) did not ignore the
Stefan> text after point.
Forwarded to the ding list in case any changes need to be made to how
gnus prompts for output filenames....
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next parent reply other threads:[~2008-06-29 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3prq05zf6.fsf@lugabout.jhcloos.org>
[not found] ` <jwv63rsh2c6.fsf-monnier+emacsbugreports@gnu.org>
2008-06-29 15:06 ` James Cloos [this message]
2008-06-29 17:26 ` Stefan Monnier
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=m3vdzs46vy.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=ding@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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.
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 NNTP newsgroup(s).