zsh-users
 help / color / mirror / code / Atom feed
From: "Daniel Shahaf" <d.s@daniel.shahaf.name>
To: "Ahmad Ismail" <ismail783@gmail.com>
Cc: "Zsh Users" <zsh-users@zsh.org>
Subject: Re: another issue with `git diff` (was: zstyle tag-order completion issue)
Date: Wed, 09 Sep 2020 20:58:29 +0000	[thread overview]
Message-ID: <3210bb98-4aab-442a-87eb-49d3fbdb29df@www.fastmail.com> (raw)
In-Reply-To: <CAHAhJwK1xzo_DM6B30iMaW1OyHSYR4gg=7mi7-A317m_RQq-Qg@mail.gmail.com>

Ahmad Ismail wrote on Wed, 09 Sep 2020 20:49 +00:00:
> zstyle -e :completion::complete:git-diff:argument-rest: tag-order 
> changed-in-working-tree-files _next_tags

First, remove the -e.  That'll address the error you reported.

Second, _next_tags is not a tag; it's a widget (= a shell function that
can be bound to a keystroke).  It doesn't belong in the value of the tag-
order style.

When you set «tag-order foo bar baz», you'll find that only completions
under the tag foo are displayed at first.  To display completions of the
tag bar, you'll have to invoke _next_tags.  However, as a widget, it's
not invoked by typing out its name; rather, it's invoked by pressing
whichever key combination or chord is bound to it.  That's explained in
the manual, under tag-order and _next_tags (they both have entries).

Cheers,

Daniel


      reply	other threads:[~2020-09-09 20:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09 12:33 zstyle tag-order completion issue Ahmad Ismail
2020-09-09 18:03 ` Daniel Shahaf
2020-09-09 20:17   ` Ahmad Ismail
2020-09-09 20:27     ` Ahmad Ismail
2020-09-09 23:37       ` Ahmad Ismail
2020-09-09 18:09 ` another issue with `git diff` (was: zstyle tag-order completion issue) Daniel Shahaf
2020-09-09 20:49   ` Ahmad Ismail
2020-09-09 20:58     ` Daniel Shahaf [this message]

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=3210bb98-4aab-442a-87eb-49d3fbdb29df@www.fastmail.com \
    --to=d.s@daniel.shahaf.name \
    --cc=ismail783@gmail.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).