git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [BUG] Autocompletion fails with "bash: words: bad array subscript"

From
Sverre Rabbelier <srabbelier@gmail.com>
Date
May 10, 2011, 20:47 UTC
Message-ID
<BANLkTi=0r_hCgt3wh4EkRqS6gnCyyKrY2g@mail.gmail.com>
In-Reply-To
<20110510203943.GH14456@sigill.intra.peff.net>
Heya,
[also +Jonathan, who I seem to have forgotten to cc]
On Tue, May 10, 2011 at 22:39, Jeff King <peff@peff.net> wrote:
Show 6 quoted lines
> Hrm. That code doesn't appear in our completion at all. We provide our
> own _get_comp_words_by_ref, but if it is already defined, we use
> whatever is there. So on my box, the problematic code comes from
> /etc/bash_completion. And I think it is a bug there, as this is one of
> the first things called (so git's completion hasn't had a change to
> introduce any bugs yet :) ).

Most curious, since it doesn't happen when I don't source git completion. Perhaps it'll happen for any completion, or maybe we're using the completion wrong somehow? I'm on Debian wheezy/sid.

-- 
Cheers,

Sverre Rabbelier
Previous: Jeff KingNext: Jeff King
Message 4 of 12 in “[BUG] Autocompletion fails with "bash: words: bad array subscript"”
  1. Sverre RabbelierMay 10, 2011
  2. Jeff KingMay 10, 2011
  3. Jeff KingMay 10, 2011
  4. Sverre RabbelierMay 10, 2011
  5. Jeff KingMay 10, 2011
  6. Sverre RabbelierMay 10, 2011
  7. Jeff KingMay 10, 2011
  8. SZEDER GáborMay 10, 2011
  9. Jonathan NiederMay 10, 2011
  10. SZEDER GáborMay 11, 2011
  11. completion: fix array indexing error after reverse history searchSZEDER Gábor, May 10, 2011
  12. Sverre RabbelierMay 10, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.