From: Eli Zaretskii <eliz@gnu.org>
To: Cameron Norton <cameron.norton@gmail.com>
Cc: 59674@debbugs.gnu.org
Subject: bug#59674: 28.2; icomplete-force-complete Incorrectly Completes Filename Case
Date: Tue, 29 Nov 2022 15:28:43 +0200 [thread overview]
Message-ID: <838rjtnb3o.fsf@gnu.org> (raw)
In-Reply-To: <87tu2i4dlg.fsf@gmail.com> (message from Cameron Norton on Mon, 28 Nov 2022 19:55:06 -0800)
> From: Cameron Norton <cameron.norton@gmail.com>
> Date: Mon, 28 Nov 2022 19:55:06 -0800
>
>
> Using icomplete, I often navigate to certain files by using a single
> character for each component of the path name before completing with
> icomplete-force-complete, which I have bound to <tab> while in the
> minibuffer. So a file
>
> ./foo/bar/baz/asdf.txt
>
> would be visited via the sequence
>
> C-x C-f f/b/b/a <tab> <return>
>
> Using icomplete-force-complete this way emulates the <tab> behavior in
> completion packages like Vertico without the extra dependency.
>
> However, with completion case sensitivity disabled, this sometimes
> results in the file's path being completed incorrectly with regards to
> capitalization. This is very noticeable when finding files in the usual
> subdirectories of $HOME, with ~/doc <tab> completing to ~/documents/
> rather than ~/Documents/, for example.
I cannot reproduce what you describe. I see a completely different
behavior: as soon as I type ~/d/m M-C-i, ~/Documents disappears from the
completions, and I see only ~/dir/moo ("dir" is another directory I have
under my home directory).
So I'm not sure why you see what you see: perhaps there's some step missing
in the recipe?
next prev parent reply other threads:[~2022-11-29 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 3:55 bug#59674: 28.2; icomplete-force-complete Incorrectly Completes Filename Case Cameron Norton
2022-11-29 13:28 ` Eli Zaretskii [this message]
2022-11-29 14:23 ` Gregory Heytings
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=838rjtnb3o.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59674@debbugs.gnu.org \
--cc=cameron.norton@gmail.com \
/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).