From: Jonathan Nieder <jrnieder@gmail.com>
To: "SZEDER Gábor" <szeder@ira.uka.de>
Cc: Jeff King <peff@peff.net>,
Sverre Rabbelier <srabbelier@gmail.com>,
Git List <git@vger.kernel.org>,
"Shawn O. Pearce" <gsoc@spearce.org>,
Stephen Boyd <bebarino@gmail.com>
Subject: Re: [BUG] Autocompletion fails with "bash: words: bad array subscript"
Date: Tue, 10 May 2011 18:45:52 -0500 [thread overview]
Message-ID: <20110510234552.GG1994@elie> (raw)
In-Reply-To: <20110510223935.GA31029@goldbirke>
SZEDER Gábor wrote:
> Thinking a bit more about it, you don't even need to search history to
> reproduce.
Yep. Doing
$ . /etc/bash_completion
$ ls<^A><TAB>
bash: words: bad array subscript
produces the same.
> So the bug is definitely not git-related. The fix would be a check
> along the lines of the first two hunks of the patch I just sent out.
FWIW it looks like the bash-completion lib adopted a different fix
recently: see [1] (_init_completion: Indicate that completion should
not continue if cword == 0, 2011-05-02).
[1] http://git.debian.org/?p=bash-completion/bash-completion.git;a=commitdiff;h=457dbf6061eea5f2d1e3bccacf1691265f7321cc
next prev parent reply other threads:[~2011-05-10 23:46 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
2011-05-10 21:10 ` Jeff King
2011-05-10 22:39 ` SZEDER Gábor
2011-05-10 23:45 ` Jonathan Nieder [this message]
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=20110510234552.GG1994@elie \
--to=jrnieder@gmail.com \
--cc=bebarino@gmail.com \
--cc=git@vger.kernel.org \
--cc=gsoc@spearce.org \
--cc=peff@peff.net \
--cc=srabbelier@gmail.com \
--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).