From: Lars Ingebrigtsen <larsi@gnus.org>
To: Andrii Kolomoiets <andreyk.mad@gmail.com>
Cc: Ole Laursen <olau@iola.dk>, 19031@debbugs.gnu.org
Subject: bug#19031: 24.4; find-file in icomplete-mode shows completions with no input
Date: Sun, 06 Dec 2020 13:46:29 +0100 [thread overview]
Message-ID: <878sabf6fu.fsf@gnus.org> (raw)
In-Reply-To: <m2mtyter9u.fsf@gmail.com> (Andrii Kolomoiets's message of "Fri, 04 Dec 2020 13:37:17 +0200")
Andrii Kolomoiets <andreyk.mad@gmail.com> writes:
> When the `icomplete-show-matches-on-no-input` variable is nil,
> completions will be not shown while minibuffer is empty:
>
> 1. emacs -Q
> 2. M-x icomplete-mode
> 3. M-x
> => No completions
> 4. f
> => Completions
> 5. C-/
> => No completions
Ah, I was misunderstanding what I was seeing... I've now reverted my
patch and reformulated as you suggest:
> Maybe it would be better to replace the text
>
> "When non-nil, show completions when first prompting for input."
>
> with something like
>
> "When non-nil, show completions when minibuffer is empty."
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-12-06 12:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 11:25 bug#19031: 24.4; find-file in icomplete-mode shows completions with no input Ole Laursen
2020-12-04 10:35 ` Lars Ingebrigtsen
2020-12-04 11:37 ` Andrii Kolomoiets
2020-12-06 12:46 ` Lars Ingebrigtsen [this message]
2020-12-07 11:43 ` Ole Laursen
2020-12-08 8:51 ` Juri Linkov
2020-12-08 10:43 ` Andrii Kolomoiets
2020-12-08 13:29 ` Lars Ingebrigtsen
2020-12-08 15:34 ` Eli Zaretskii
2020-12-08 16:16 ` Andrii Kolomoiets
2020-12-08 17:09 ` Ole Laursen
2020-12-08 19:11 ` Juri Linkov
2020-12-08 21:33 ` Andrii Kolomoiets
2020-12-09 19:08 ` Juri Linkov
2020-12-10 8:08 ` Andrii Kolomoiets
2020-12-14 8:44 ` Juri Linkov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878sabf6fu.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=19031@debbugs.gnu.org \
--cc=andreyk.mad@gmail.com \
--cc=olau@iola.dk \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.