From: Tomasz Pala <firstname.lastname@example.org>
To: Roman Perepelitsa <email@example.com>
Cc: Mikael Magnusson <firstname.lastname@example.org>, Zsh Users <email@example.com>
Subject: Re: completion: lookup argument using descriptions
Date: Wed, 16 Jun 2021 12:04:21 +0200 [thread overview]
Message-ID: <20210616100421.GA11541@polanet.pl> (raw)
On Sun, Jun 13, 2021 at 12:43:46 +0200, Roman Perepelitsa wrote:
>> How do you know about the 'search' option?
> I don't remember how I discovered it. Now I just know it exists.
zstyle ':completion:*' menu select=1 interactive
The last one is really interesting, although I experience the same
(1) problem as described and presented here:
(2) blocks tab from going into menu selection (one have to use arrows),
(3) doesn't start again after using arrows,
so I won't use this.
> For completeness sake, it's also possible (albeit not easy) to display
> zsh completions using an external command. For example, in my zsh
> setup completions are displayed with fzf. Here's how it looks:
Thanks a lot for new ideas:) It took me another 2 days to review
fzf-related projects and I've ended up with:
bindkey -M emacs '^f' fzf_completion (from fzf-tab-completion)
bindkey -M emacs '^R' fzf-history-widget (fzf/shell/key-bindings.zsh)
These 2 seems reasonable and working well when called on purpose:
- fzf_completion to search for descriptions of "-- described" options,
- fzf-history-widget for convenience.
Other fzf completions seem disruptive for me and break my CLI flow,
making the work less smooth and effectively slower than pure zsh.
Tomasz Pala <firstname.lastname@example.org>
prev parent reply other threads:[~2021-06-16 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 9:30 Tomasz Pala
2021-06-10 9:45 ` Roman Perepelitsa
2021-06-10 10:09 ` Mikael Magnusson
2021-06-13 10:06 ` Tomasz Pala
2021-06-13 10:43 ` Roman Perepelitsa
2021-06-16 10:04 ` Tomasz Pala [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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 NNTP newsgroup(s).