unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 14175@debbugs.gnu.org
Subject: bug#14175: 24.3.50; Bad completion behavior with read-file-name-completion-ignore-case t
Date: Tue, 24 Aug 2021 17:20:51 +0200	[thread overview]
Message-ID: <87zgt6j2cs.fsf@web.de> (raw)
In-Reply-To: <87lf4tug3z.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 23 Aug 2021 03:03:44 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> I can't reproduce either of these issues in Emacs 28.  Are you still
> seeing this in recent Emacs versions?

The first part is still the same (anything that followed seems to be
fixed), but after reading again the docstring of `completion-auto-help',
I think not to pop up *Completions* seem to be intended since that
completion attempt does not count as unsuccessful:

> Michael Heerdegen <michael_heerdegen@web.de> writes:
>
> > (setq read-file-name-completion-ignore-case t
> >       completion-auto-help t)
> >
> > In my "~/", I have, among other files,
> >
> >   lrwxrwxrwx   1 micha micha    9 Feb  3 20:00 download -> Downloads
> >   drwxr-xr-x  11 micha micha 4,0K Apr  9 15:40 Downloads
> >
> > I hit C-x d ~/Down TAB
> >
> > Emacs completes the minibuffer to
> >
> >   ~/Download
> >
> > Since this is no valid completion, it should pop up *Completions*, but
> > it doesn't (first issue).

So I think we are done here and you can close this report.

Thanks,

Michael.





  reply	other threads:[~2021-08-24 15:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10 20:26 bug#14175: 24.3.50; Bad completion behavior with read-file-name-completion-ignore-case t Michael Heerdegen
2013-04-10 23:08 ` Michael Heerdegen
2013-04-12 14:53   ` Michael Heerdegen
2013-04-12 17:40   ` Stefan Monnier
2021-08-23  1:03 ` Lars Ingebrigtsen
2021-08-24 15:20   ` Michael Heerdegen [this message]
2021-08-24 15:25     ` Lars Ingebrigtsen

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=87zgt6j2cs.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=14175@debbugs.gnu.org \
    --cc=larsi@gnus.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).