From: Jeff King <peff@peff.net>
To: "Дилян Палаузов" <Dilyan.Palauzov@aegee.org>
Cc: git@vger.kernel.org
Subject: Re: bash completion with 2.18.0/maint: unknown options
Date: Sat, 14 Jul 2018 17:24:33 -0400 [thread overview]
Message-ID: <20180714212433.GB6430@sigill.intra.peff.net> (raw)
In-Reply-To: <d9272a12c2a38429857777f7811010956b7b6ed5.camel@aegee.org>
On Sat, Jul 14, 2018 at 02:46:17PM +0000, Дилян Палаузов wrote:
> After upgrading to 2.18 the completion does not work:
>
> typing "git de<TAB>" prints
> my@host:~$ git deUnknown option: --list-cmds=list-
> mainporcelain,others,nohelpers,alias,list-complete,config
> usage: git [--version] [--help] [-C <path>] [-c name=value]
> [...]
In v2.18, the completions are generated programatically using new
options added to the git binary. The completion and the git binary
you're using have to be upgraded in lockstep (this has always been the
case, though I think this is probably the case where not doing so would
have the biggest effect).
Are you sure the git binary you're running matches the completion?
You mentioned that you're sourcing the completion from a clone in
/git/git. What does `type git` report?
-Peff
next prev parent reply other threads:[~2018-07-14 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-14 14:46 bash completion with 2.18.0/maint: unknown options Дилян Палаузов
2018-07-14 21:24 ` Jeff King [this message]
2018-07-14 21:38 ` Дилян Палаузов
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=20180714212433.GB6430@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Dilyan.Palauzov@aegee.org \
--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.
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).