zsh-users
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Are completions in some way heavy?
Date: Fri, 10 Jun 2016 14:22:55 +0200	[thread overview]
Message-ID: <CAKc7PVBK0Ev6tMqiajjfWgXVSyLqHpmTjG1hshMZvUozznKtJw@mail.gmail.com> (raw)
In-Reply-To: <160608114009.ZM807@torch.brasslantern.com>

On 8 June 2016 at 20:40, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Jun 8, 11:03am, Oliver Kiddle wrote:
> } Menu selection (the zsh/complist module) has an incremental search, so
> } what you describe above can already be done.
>
> I think Sebastian wants to search through the descriptions, whereas the
> complist search only examines the completions themselves.

It searches through descriptions of options. Quite nice thing. This
single zstyle:

zstyle ':completion:*:*:*:default' menu yes select search

configures the completion to a high degree I think. Often "force-list"
is used and I think other combinations of zstyles to actually see menu
completion. Works quite well, more enters are required but it's done
to be quite natural. Don't know yet how to cycle through matches,
would like to leave completion on space, don't get what "interactive"
mode is. But a very nice thing, I had success of finding mpv
--no-video option without ever giving options to the program before
and considering it's -vo null like in mplayer. Nevertheless I need to
recognize this more.

And nevertheless I decided to continue with the proof of concept :)

https://asciinema.org/a/8k8v5ni5lnnpoc3z5jzl6jgav
https://github.com/psprint/zzcomplete

What I think is needed is context search, to return text surrounding
matches. Might be difficult to implement and unreadable (like grep -C,
it's difficult to read when untrained).

Best regards,
Sebastian Gniazdowski


  reply	other threads:[~2016-06-10 12:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06 12:43 Sebastian Gniazdowski
2016-06-06 16:01 ` Bart Schaefer
2016-06-06 19:28   ` Sebastian Gniazdowski
2016-06-07 20:44     ` Bart Schaefer
2016-06-08  4:34       ` Sebastian Gniazdowski
2016-06-08  9:03         ` Oliver Kiddle
2016-06-08 18:40           ` Bart Schaefer
2016-06-10 12:22             ` Sebastian Gniazdowski [this message]
2016-06-10 17:42               ` Bart Schaefer
2016-06-11  7:15                 ` Sebastian Gniazdowski
2016-06-11 17:18                   ` Bart Schaefer
2016-06-11 17:44                     ` Sebastian Gniazdowski
     [not found]           ` <160608114009.ZM807__13786.2274809324$1465411295$gmane$org@torch.brasslantern.com>
2016-06-10 17:35             ` Daniel Shahaf
2016-06-10 19:49               ` Bart Schaefer
     [not found] ` <160606090104.ZM11947__15732.477248139$1465228961$gmane$org@torch.brasslantern.com>
2016-06-07 22:53   ` Daniel Shahaf

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=CAKc7PVBK0Ev6tMqiajjfWgXVSyLqHpmTjG1hshMZvUozznKtJw@mail.gmail.com \
    --to=sgniazdowski@gmail.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-users@zsh.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.vuxu.org/mirror/zsh/

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).