From: Eli Zaretskii <eliz@elta.co.il>
Subject: Re: Change default behavior of completion-ignored-extensions
Date: 02 Dec 2003 08:19:55 +0200 [thread overview]
Message-ID: <uptf7hhbo.fsf@elta.co.il> (raw)
In-Reply-To: <m27k1ggkbk.fsf@Andrew-Kortys-Computer.local> (message from Andrew Korty on Mon, 01 Dec 2003 19:00:31 -0500)
> From: Andrew Korty <ajk@iu.edu>
> Date: Mon, 01 Dec 2003 19:00:31 -0500
>
> I'd like to add ./ and ../ to this variable and be able to
> tab-complete right through a directory with only one interesting
> entry.
Emacs already filters out the uninteresting directory entries such as
"." and "..". This happens automatically; the value of
completion-ignored-extensions does not need to include them.
> For example, if I have a directory ~/foo/ containing a
> subdirectory bar/, I should be able to type
>
> M-x find-file RET ~/foo TAB
>
> and end up with ~/foo/bar/ in the minibuffer instead of first getting
> "[Complete, but not unique]", hitting TAB again, getting
> "Completion List" buffer containing ./, ../, and bar/, and having to
> type "b TAB" to finally get what should have been obvious.
What version of Emacs do you have there? In Emacs 21.2, I type "C-x
C-f ~/foo TAB" and Emacs completes it to "~/foo/". Another TAB gets
me "~/foo/bar/", just like I'd expect. There are no "[Complete, but
not unique]" messages and no need to wade through useless completion
lists.
(The reason that you need 2 TABs to get what you want is because you
might wish to create a new file in ~/foo. This is a well-documented
feature, unrelated to `completion-ignored-extensions'.)
next prev parent reply other threads:[~2003-12-02 6:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 0:00 Change default behavior of completion-ignored-extensions Andrew Korty
2003-12-02 6:19 ` Eli Zaretskii [this message]
2003-12-02 14:43 ` Andrew Korty
2003-12-02 17:38 ` Eli Zaretskii
2003-12-10 12:29 ` Andrew Korty
-- strict thread matches above, loose matches on Subject: below --
2003-12-02 0:00 Andrew Korty
2003-12-01 23:59 Andrew Korty
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=uptf7hhbo.fsf@elta.co.il \
--to=eliz@elta.co.il \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).