zsh-users
 help / color / mirror / code / Atom feed
From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Completion introspection
Date: Mon, 1 Jun 2020 10:22:17 +0200	[thread overview]
Message-ID: <CAN=4vMpeKYvyju4rpaSvBzjhznN=8VbJmMYhj_TEz9-bBaFARw@mail.gmail.com> (raw)
In-Reply-To: <20200601080730.7d373c99@tarpaulin.shahaf.local2>

On Mon, Jun 1, 2020 at 10:07 AM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> What problem are you trying to solve?

In addition to regular tab completion (expand-or-complete) I have
another key binding for file completion with fzf. If I complete `vi
./` with tab, it'll ask me to choose the first path segment. If I
complete it with alt-i (my fzf file completion binding), I'll be
presented with fuzzy search UI over all files in the current directory
(recursively).

Unfortunately, alt-i binding doesn't work very well. It tries to guess
which word is being completed and which command but it does it without
involving the standard zsh completion system, so it fails often. I'm
trying to improve it.

Maybe there is another way? Perhaps it's possible to configure zsh
completion system so that all file completions are recursive? My tab
binding is actually also using fzf if there are multiple possible
completions, so if file completions were recursive, that would work.

> Why must the widget not be a completion widget?

I'm not sure if it must be. The current widget isn't a completion
widget and I know how to fix it if only I knew how to get the bits of
information I asked about (the word that would be completed if I
pressed tab, etc.).

Roman.

  reply	other threads:[~2020-06-01  8:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-31  8:44 Roman Perepelitsa
2020-06-01  8:07 ` Daniel Shahaf
2020-06-01  8:22   ` Roman Perepelitsa [this message]
2020-06-02 13:43     ` Oliver Kiddle
2020-07-01 17:46       ` Roman Perepelitsa

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='CAN=4vMpeKYvyju4rpaSvBzjhznN=8VbJmMYhj_TEz9-bBaFARw@mail.gmail.com' \
    --to=roman.perepelitsa@gmail.com \
    --cc=d.s@daniel.shahaf.name \
    --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).