From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Tim Jaacks <timjaacks@posteo.de>
Cc: git@vger.kernel.org
Subject: Re: Bash completion for git aliases containing nested subcommands
Date: Mon, 3 Oct 2022 17:43:54 +0200 [thread overview]
Message-ID: <20221003154354.GC7659@szeder.dev> (raw)
In-Reply-To: <1839e62f930.285a.8a94aeaa49923dfb9a7d55a303990d0a@posteo.de>
On Mon, Oct 03, 2022 at 03:07:10PM +0000, Tim Jaacks wrote:
> Hi Gabor,
>
> thanks a lot for your detailed reply! I tried that and it works, thank you.
>
> Just another small follow-up question, out of curiosity: I noticed that zsh
> handles the alias completion correctly out of the box (using the exact same
> gitconfig file). I don't have any dedicated zsh completion file, just
> installed zsh via apt. Do you know why and how zsh handles this differently?
There are not only one but two Zsh completion scripts for Git:
- Ours, which is essentially a wrapper around our Bash completion
script, so it shouldn't work for your alias, and it has to be
installed manually, so I doubt that this is what you tried.
- One that's shipped with Zsh, with all the bells and whistles that
Zsh's completion system offers. It's not maintained by the Git
project, and I have no idea how it works, but I guess it works
sufficiently differently to make your use case work.
next prev parent reply other threads:[~2022-10-03 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 11:45 Bash completion for git aliases containing nested subcommands Tim Jaacks
2022-10-03 14:24 ` SZEDER Gábor
[not found] ` <1839e62f930.285a.8a94aeaa49923dfb9a7d55a303990d0a@posteo.de>
2022-10-03 15:11 ` Tim Jaacks
2022-10-03 15:43 ` SZEDER Gábor [this message]
2022-10-03 22:24 ` Jeff King
2022-10-04 11:21 ` Tim Jaacks
2022-10-05 10:05 ` SZEDER Gábor
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=20221003154354.GC7659@szeder.dev \
--to=szeder.dev@gmail.com \
--cc=git@vger.kernel.org \
--cc=timjaacks@posteo.de \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.