unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ergus <spacibba@aol.com>
To: Juri Linkov <juri@linkov.net>
Cc: emacs-devel@gnu.org
Subject: Re: zsh-like zcomplete-mode based on icomplete-mode
Date: Sun, 10 Apr 2022 23:45:39 +0200	[thread overview]
Message-ID: <20220410214539.e5dg462wpc7tfo76@Ergus> (raw)
In-Reply-To: <86o818bvgl.fsf@mail.linkov.net>

On Sun, Apr 10, 2022 at 10:16:10PM +0300, Juri Linkov wrote:
>> Ok, now it works better... But this is not zsh completion anymore ;) The
>> dynamic table auto-refresh is nice for people who like icomplete/ido but
>> it is a different use case and after a while it starts becoming annoying
>> for quick uses... but this is a personal preference probably.
>
>zsh does the same when configured with
>
>  zstyle ':completion:*' menu select interactive
>
Yes we already mention that, but such behavior is not the default, wo
when we say zsh behavior, that's not usually what a zsh user expects.

>So we should have a variable to enable/disable interactive auto-refresh.
>
>> On the other hand I cannot use the up and down arrows anymore for search
>> in the history with commands like previous-complete-history-element
>
>Another variable could provide at least 3 choices:
>
>1. never enable arrows, then use only special keys like
>   in icomplete-mode C-./C-, but this is not quite convenient;
>
This will be like not having the zcomplete-mode enabled right?

>2. always enable arrows like in icomplete-vertical-mode,
>   but this disables history navigation;
>
>3. enable arrows only when the Completions window is displayed,
>   this assumes that auto-refresh is disabled, otherwise
>   the Completions window is displayed almost always.
>
This is in my opinion the only real zsh like behavior. If completions
are not visible, it does not make sense to enable arrow navigation.

>> There is a detail when completion-format is one-column and it is when
>> using zcomplete-previous-line-completion, some candidates are not
>> highlighted... when we go to the last candidate and return... It seems
>> like the cursor goes at the end of the candidate where the face-cursor
>> is not set.
>
>This looks like bug#54374.

No, this only happens with the minibuffer navigation... with normal
navigation in completions there is not issue for me.



  reply	other threads:[~2022-04-10 21:45 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       ` [External] : " Drew Adams
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 [this message]
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

  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=20220410214539.e5dg462wpc7tfo76@Ergus \
    --to=spacibba@aol.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    /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).