git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Pratyush Yadav <me@yadavpratyush.com>
To: git@vger.kernel.org
Subject: completion: checkout.* not being completed in zsh
Date: Fri, 16 Aug 2019 01:20:27 +0530	[thread overview]
Message-ID: <20190815185901.btf4d7c4ewsccxuu@localhost.localdomain> (raw)

Hi everyone,

I just noticed that checkout.* is not being completed in zsh. I wanted 
to set checkout.defaultRemote, but zsh would not auto-complete it.

When I do:

$ git config check<Tab>

zsh does not auto-fill "checkout."

Doing the same in bash works, so the functionality is there, it just 
doesn't work in zsh.

Once I add checkout.defaultRemote to my git config, autocompletion 
starts working, but only for defaultRemote, even though checkout has two 
options: defaultRemote and optimizeNewBranch.

To make it clear, this is what happens once I have added 
checkout.defaultRemote to my config:

$ git config check<Tab>
$ git config checkout.  # Completes to "checkout.". Correct behaviour.
$ git config checkout.<Tab>

# Completes to defaultRemote, even though it should ask between 
# defaultRemote and optimizeNewBranch
$ git config checkout.defaultRemote

I tried looking at contrib/completion, and I can see that zsh completion 
works on top of bash completion, so I don't know why exactly it works 
for bash but not for zsh.

I am not too familiar with how these auto completion scripts work, so if 
someone can point me in the right direction, I'll see if I can figure 
out a fix and submit it here.

-- 
Regards,
Pratyush Yadav

             reply	other threads:[~2019-08-15 19:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-15 19:50 Pratyush Yadav [this message]
2019-08-16  2:36 ` completion: checkout.* not being completed in zsh brian m. carlson
2019-08-17 14:00   ` Pratyush Yadav

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: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190815185901.btf4d7c4ewsccxuu@localhost.localdomain \
    --to=me@yadavpratyush.com \
    --cc=git@vger.kernel.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://80x24.org/mirrors/git.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).