From: Ole Laursen <olau@iola.dk>
To: Andrii Kolomoiets <andreyk.mad@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
19031@debbugs.gnu.org, juri@linkov.net
Subject: bug#19031: 24.4; find-file in icomplete-mode shows completions with no input
Date: Tue, 8 Dec 2020 18:09:38 +0100 [thread overview]
Message-ID: <CANb2OvJNntmduDZEF_Ji=_qE3mEfXyV_zZaaSjO6hGCkp8_HNQ@mail.gmail.com> (raw)
In-Reply-To: <m2y2i8xohh.fsf@gmail.com>
Den tir. 8. dec. 2020 kl. 17.16 skrev Andrii Kolomoiets <andreyk.mad@gmail.com>:
> Yes. It's not about filtering out dotfiles but about to make icomplete
> to not show completions until user starts typing filename. Completions
> (including dotfiles) will be shown when user will type e.g. ".e" or when
> the 'icomplete-show-matches-on-no-input' variable is t.
So conceptually chop the path up and consider each component of it a
separate completion task? I think that is a good match for how I'm
going about it.
Ole
next prev parent reply other threads:[~2020-12-08 17:09 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
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 [this message]
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
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='CANb2OvJNntmduDZEF_Ji=_qE3mEfXyV_zZaaSjO6hGCkp8_HNQ@mail.gmail.com' \
--to=olau@iola.dk \
--cc=19031@debbugs.gnu.org \
--cc=andreyk.mad@gmail.com \
--cc=juri@linkov.net \
--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).