From: Andrew Korty <ajk@iu.edu>
Subject: Change default behavior of completion-ignored-extensions
Date: Mon, 01 Dec 2003 18:59:06 -0500 [thread overview]
Message-ID: <m2d6b8gkdx.fsf@Andrew-Kortys-Computer.local> (raw)
Greetings. How can I change the way completion-ignored-extensions is
used by find-file?
As it is, "lists of possible completions" aren't affected by this
variable:
,----[ C-h v completion-ignored-extensions RET ]
| Documentation:
| *Completion ignores filenames ending in any string in this list.
| This variable does not affect lists of possible completions,
| but does affect the commands that actually do completions.
`----
I'd like to add ./ and ../ to this variable and be able to
tab-complete right through a directory with only one interesting
entry. 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.
I understand that completion-ignored-extensions is not supposed to
work this way, but I want to change that behavior. It seems like I
should be able to advise minibuffer-complete, but I haven't figured
out how to do that successfully.
--
Andrew J. Korty, Principal Security Engineer, GCIA, GCFA
Office of the Vice President for Information Technology
Indiana University
next reply other threads:[~2003-12-01 23:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 23:59 Andrew Korty [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-02 0:00 Change default behavior of completion-ignored-extensions Andrew Korty
2003-12-02 0:00 Andrew Korty
2003-12-02 6:19 ` Eli Zaretskii
2003-12-02 14:43 ` Andrew Korty
2003-12-02 17:38 ` Eli Zaretskii
2003-12-10 12:29 ` 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=m2d6b8gkdx.fsf@Andrew-Kortys-Computer.local \
--to=ajk@iu.edu \
/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).