Your message dated Sun, 2 Dec 2018 11:40:52 -0200
with message-id <[email protected]>
and subject line Re: bash completion COMP_WORDS bad array subscript
has caused the Debian Bug report #559953,
regarding bash completion COMP_WORDS bad array subscript
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
559953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559953
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bash
Version: 4.0-4
typing "make >& make" and then hitting tab produces the error "-bash:
COMP_WORDS: bad array subscript"
--- End Message ---
--- Begin Message ---
There are several issues reported in this thread. I'll go through each
of them, and since they are no longer reproducible, I'll close the bug.
On Mon, 7 Dec 2009 18:14:40 -0500 Peter <[email protected]> wrote:
>
> typing "make >& make" and then hitting tab produces the error "-bash:
> COMP_WORDS: bad array subscript"
With current code, this works as expected:
$ make >& make[TAB]
make makeglossaries
makeconv makeglossaries-lite
makedtx makeindex
make-first-existing-target makejvf
On Sun, 09 Jan 2011 13:38:21 +0100 xiscu <[email protected]> wrote:
>
> I'm getting this error in also in the version mentioned above.
>
> To reproduce:
> $/usr/bin/python <TAB here>
>
> Expected:
> - List of files
>
> Result:
> $/usr/bin/python bash: COMP_WORDS: bad array subscript
Likewise:
$ ls
dir1 dir2 file1 file2
$ /usr/bin/python
dir1/ dir2/
On Tue, 26 Apr 2011 18:46:35 +0200 tictacbum <[email protected]> wrote:
>
> This message also appears when you press tab with the cursor at the
> beginning of certain commands.
> To reproduce this write "dpkg" move cursor above "d" and hit tab, this one
> is specially annoying since message is repeated until you press ctrl-c
> This happens a lot to me when I use reverse-i-search (ctrl-r) and I press
> tab by mistake
> similar behavior with ls, cp, grep, ssh, man, uname, chown...
Likewise:
$ uname
^- place cursor here and hit TAB
unalias uname
I'm closing this bug, since it is no longer reproducible. If you have
more information and would like to reopen the bug (or create a new
one), please do not hesitate to do so.
Thank you all for the reports.
--- End Message ---
