GNU bug report logs - #19031
24.4; find-file in icomplete-mode shows completions with no input

Previous Next

Package: emacs;

Reported by: Ole Laursen <olau <at> iola.dk>

Date: Wed, 12 Nov 2014 16:42:02 UTC

Severity: normal

Tags: fixed

Found in version 24.4

Fixed in version 28.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Ole Laursen <olau <at> iola.dk>
Cc: 19031 <at> debbugs.gnu.org
Subject: bug#19031: 24.4; find-file in icomplete-mode shows completions with no input
Date: Fri, 04 Dec 2020 11:35:22 +0100
Ole Laursen <olau <at> iola.dk> writes:

> Run emacs -Q, evaluate
>
>   (icomplete-mode 1)
>
> then press C-x C-f and wait a second. There's now completions in the
> minibuffer despite icomplete-show-matches-on-no-input being nil. Perhaps
> icomplete is confused by the current working dir being present in C-x
> C-f.

I think the icomplete-show-matches-on-no-input doc string is just
unclear here.  It seems like the point of the variable is that you can
set it to non-nil to force icomplete to wait until we have completions
before displaying the prompt?  When it's the default nil value, it'll
still show all the matches, but they may arrive asynchronously.

I've now clarified this in the doc string in Emacs 28.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no




This bug report was last modified 4 years and 220 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.