From: Visuwesh <visuweshm@gmail.com>
To: Markus Triska <triska@metalevel.at>
Cc: 67830@debbugs.gnu.org
Subject: bug#67830: 30.0.50; find-file completion sometimes unexpectedly omits directories
Date: Fri, 15 Dec 2023 09:43:28 +0530 [thread overview]
Message-ID: <87h6kkrtlj.fsf@gmail.com> (raw)
In-Reply-To: <m2ttokv1r2.fsf@metalevel.at> (Markus Triska's message of "Thu, 14 Dec 2023 23:49:05 +0100")
[Thursday December 14, 2023] Markus Triska wrote:
> To reproduce this issue, please first create the directory ~/issue/.git,
> and the file ~/issue/.gitignore, for example with:
>
> $ mkdir issue
> $ cd issue/
> $ mkdir .git
> $ touch .gitignore
>
> Then, from your home directory, start Emacs with:
>
> $ emacs -Q
>
> and do:
>
> C-x C-f ~/issue/.git TAB
>
> As expected, the minibuffer displays:
>
> [Complete, but not unique]
>
> and Emacs also shows the 2 possible completions:
>
> 2 possible completions:
> .git/
> .gitignore
>
> In contrast, when I do:
>
> C-x C-f ~/issue/. TAB
>
> then the minibuffer prematurely completes it to the file:
>
> ~/issue/.gitignore
>
> This is even though the directory ~/issue/.git exists, and also forms a
> valid and expected completion of "~/issue/.".
>
> The expected behaviour is the same as above, on the grounds that
> "~/issue/." is a proper prefix of "~/issue/.git" and therefore should
> never yield fewer possible completions.
>
> Thank you and all the best,
> Markus
>
Completion is working as intended, AFAIU. Have a look at
completion-ignored-extensions.
next prev parent reply other threads:[~2023-12-15 4:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 22:49 bug#67830: 30.0.50; find-file completion sometimes unexpectedly omits directories Markus Triska
2023-12-15 4:13 ` Visuwesh [this message]
2023-12-15 8:48 ` Eli Zaretskii
2024-01-10 11:04 ` Stefan Kangas
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=87h6kkrtlj.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=67830@debbugs.gnu.org \
--cc=triska@metalevel.at \
/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).