Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Strange behavior about option completion of `git push`
- X-seq: zsh-users 26069
- From: Yasuhiro KIMURA <yasu@xxxxxxxxxxx>
- To: zsh-users@xxxxxxx
- Subject: Strange behavior about option completion of `git push`
- Date: Fri, 18 Sep 2020 02:22:13 +0900 (JST)
- Archived-at: <https://zsh.org/users/26069>
- Archived-at: <http://www.zsh.org/sympa/arcsearch_id/zsh-users/2020-09/20200918.022213.2164194227802931452.yasu%40utahime.org>
- Authentication-results: zsh.org; iprev=pass (gate.utahime.jp) smtp.remote-ip=183.180.29.210; dkim=pass header.d=utahime.org header.s=maybe2019112701 header.a=rsa-sha256; dmarc=none header.from=utahime.org; arc=none
- Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=utahime.org; s=maybe2019112701; t=1600363423; bh=rM5mpQQTFPqIcvdnxgvzS1U25Nm2nRuYnUnC1tGgaVY=; h=Date:To:Subject:From; b=tTahDhXFhEZe71bNg1r2KXM7JVZ70Y2yk0pxmdQ8LMEc9FYrxg1N7LRAFKNOvyq2J epS/NKRhcRDqcFztyUlPkzcBwDg7WJh4Q8WUaSdNYm8mFgN0g8P2cfuyOYm8Ykn4/G Q3FRNyl27gMVltH4dqCl0fozA+aF7hj6GOAbMGXxNVdBaCZNywFIIhmHBmWmrGjTBR MAHMaGdSC+IzsVxCM/cfNj2kmuHRLEx8CUoAtEKqoo7NOTqoDDvH9wS8DyBmkzYm5B tQJd4q2HX1ZYKm5HKVLTYeNUn1sEFE7jStfgOiPDRop/9DMYmK09Cb9Rl6QG52NDPZ Y/oayCTUp+QjQ==
- List-archive: <http://www.zsh.org/sympa/arc/zsh-users>
- List-help: <mailto:sympa@zsh.org?subject=help>
- List-id: <zsh-users.zsh.org>
- List-owner: <mailto:zsh-users-request@zsh.org>
- List-post: <mailto:zsh-users@zsh.org>
- List-subscribe: <mailto:sympa@zsh.org?subject=subscribe%20zsh-users>
- List-unsubscribe: <mailto:sympa@zsh.org?subject=unsubscribe%20zsh-users>
- Sender: zsh-users-request@xxxxxxx
Hello,
I use zsh 5.8 on some OSes (CentOS, Cygwin, Debian, FreeBSD, etc.) and
found strange behavior about option completion of `git push`.
At first let's type `git push --r` and hit TAB. Then it is completed
as `git push --re`. Options of `git push` that start with `--r` are
`--receive-pack`, `--recurse-submodules` and `--repo` and all of them
start with `--re`. So it is reasonable that completion works as above.
Next let's type `git push --f' and hit TAB. In this case options that
start with `--f' are `--follow-tags`, `--force` and
`--force-with-lease` and all of them start with `--fo`. So expected
behavior is that it will be completed as `git push --fo`. But what
really happens is that there is no change after TAB is hit.
I checked definition of `_git-push` function in
/usr/share/zsh/5.8/functions/Completion/Unix/_git but didn't find the
source of the difference.
Would someone please explain why such differnce happens?
Best Regards.
---
Yasuhiro KIMURA
Messages sorted by:
Reverse Date,
Date,
Thread,
Author