From: Drew Adams <drew.adams@oracle.com>
To: Tassilo Horn <tsdh@gnu.org>, Juri Linkov <juri@linkov.net>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: zsh-like zcomplete-mode based on icomplete-mode
Date: Sun, 10 Apr 2022 16:31:08 +0000 [thread overview]
Message-ID: <SJ0PR10MB548881B503B984510E00D91BF3EB9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87ilrhuwoh.fsf@gnu.org>
> I'm not sure if it is expected that with
> zcomplete-show-matches-on-no-input enabled,
> there are no *Completions* shown initially.
> For example with C-x C-f, it would be nice to
> immediately see the contents of the current directory.
I mentioned that (1) different users have different
preferences about this, and (2) it's possible to
have different preferences for different commands
(which is likely why you cited `C-x C-f').
Icicles provides user options for this, and it
lets commands provide appropriate default behavior.
E.g., a command that essentially uses *Completions*
as a menu can show that initially (and nevertheless
also be able to change that "menu" based on user
minibuffer input (pattern filtering).
There is no reasonable one-size-fits-all. There
can be a reasonable default behavior. There need
to be user knobs to control the behavior according
to preference - and preference not only in general
but even wrt particular commands and particular
contexts.
next prev parent reply other threads:[~2022-04-10 16:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 18:45 zsh-like zcomplete-mode based on icomplete-mode Juri Linkov
2022-04-09 20:30 ` Tassilo Horn
2022-04-10 7:38 ` Juri Linkov
2022-04-10 9:12 ` Tassilo Horn
2022-04-10 16:31 ` Drew Adams [this message]
2022-04-10 19:11 ` Juri Linkov
2022-04-10 1:05 ` Ergus
2022-04-10 7:38 ` Juri Linkov
2022-04-10 10:41 ` Ergus
2022-04-10 16:34 ` [External] : " Drew Adams
2022-04-10 19:16 ` Juri Linkov
2022-04-10 21:45 ` Ergus
2022-04-11 16:53 ` Juri Linkov
2022-04-12 17:15 ` 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=SJ0PR10MB548881B503B984510E00D91BF3EB9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=tsdh@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 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.