unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Gregory Heytings <gregory@heytings.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 59674@debbugs.gnu.org, Cameron Norton <cameron.norton@gmail.com>
Subject: bug#59674: 28.2; icomplete-force-complete Incorrectly Completes Filename Case
Date: Tue, 29 Nov 2022 14:23:47 +0000	[thread overview]
Message-ID: <b073f545257dbcbfcda1@heytings.org> (raw)
In-Reply-To: <838rjtnb3o.fsf@gnu.org>


>
> 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?
>

The recipe is not incomplete, but it must be followed very carefully (it's 
really a corner case):

mkdir -p ~/Zack/foo/bar ~/zock
echo baz > ~/Zack/foo/bar/baz.txt
emacs -Q
M-x icomplete-mode RET
M-: (setq read-file-name-completion-ignore-case t) RET
M-x cd ~/zock RET
C-x C-f ~/z/f/b/b ;; only type these characters, with only lower case letters
;; at that point you should see this in the minibuffer:
;; Find file: ~/zock/~/z/f/b/b[...ack/foo/bar/baz.txt] [Matched]
C-M-i
;; now you see:
;; Find file: ~/zock/~/zack/foo/bar/baz.txt[...ack/foo/bar/baz.txt] [Matched]
RET
;; the above baz.txt file is not opened, instead a new empty file is created, and you see:
;; Use M-x make-directory RET RET to create the directory and its parent





      reply	other threads:[~2022-11-29 14:23 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
2022-11-29 14:23   ` Gregory Heytings [this message]

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=b073f545257dbcbfcda1@heytings.org \
    --to=gregory@heytings.org \
    --cc=59674@debbugs.gnu.org \
    --cc=cameron.norton@gmail.com \
    --cc=eliz@gnu.org \
    /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).