From: Sverre Rabbelier <srabbelier@gmail.com>
To: Jeff King <peff@peff.net>
Cc: "Jonathan Nieder" <jrnieder@gmail.com>,
"Git List" <git@vger.kernel.org>,
"Shawn O. Pearce" <gsoc@spearce.org>,
"SZEDER Gábor" <szeder@ira.uka.de>,
"Stephen Boyd" <bebarino@gmail.com>
Subject: Re: [BUG] Autocompletion fails with "bash: words: bad array subscript"
Date: Tue, 10 May 2011 23:02:53 +0200 [thread overview]
Message-ID: <BANLkTin9=7y+2eqUgo_ObcYeGs3TQ7YMGw@mail.gmail.com> (raw)
In-Reply-To: <20110510210116.GA25224@sigill.intra.peff.net>
Heya,
On Tue, May 10, 2011 at 23:01, Jeff King <peff@peff.net> wrote:
> Right. Bash calls into our __git() completion function, which calls the
> implementation of _get_comp_words_by_ref from /etc/bash_completion,
> which has the bug. If you don't source git completion, then you are just
> getting bash's default file completion.
So should we file this bug with bash's completion people? Also, how
did you manage to reproduce? It doesn't happen all the time for me.
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2011-05-10 21:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 20:13 [BUG] Autocompletion fails with "bash: words: bad array subscript" Sverre Rabbelier
2011-05-10 20:31 ` Jeff King
2011-05-10 20:39 ` Jeff King
2011-05-10 20:47 ` Sverre Rabbelier
2011-05-10 21:01 ` Jeff King
2011-05-10 21:02 ` Sverre Rabbelier [this message]
2011-05-10 21:10 ` Jeff King
2011-05-10 22:39 ` SZEDER Gábor
2011-05-10 23:45 ` Jonathan Nieder
2011-05-11 21:09 ` SZEDER Gábor
2011-05-10 22:14 ` [PATCH] completion: fix array indexing error after reverse history search SZEDER Gábor
2011-05-10 22:19 ` Sverre Rabbelier
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='BANLkTin9=7y+2eqUgo_ObcYeGs3TQ7YMGw@mail.gmail.com' \
--to=srabbelier@gmail.com \
--cc=bebarino@gmail.com \
--cc=git@vger.kernel.org \
--cc=gsoc@spearce.org \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
--cc=szeder@ira.uka.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 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).