[Bug 660613] Re: COMP_WORDS bad array subscript in python completion

2014-11-30 Thread Peter Cordes
There's something fishy going on, /usr/bin/python /etc/ba[TAB] => prints a single completion, but doesn't apply it. bash_completion.d/ python /etc/ba[TAB] => /etc/bash_completion.d/ I think when testing this before, I had my completion dynamic loading messed up, and wasn't getting /usr/share/

[Bug 660613] Re: COMP_WORDS bad array subscript in python completion

2014-11-29 Thread Peter Cordes
Can anyone else confirm that /usr/bin/python /etc/ba is a valid testcase for this? Or is ln -s /usr/bin/python tmp/python needed? I'm not seeing a problem on trusty with Nicolas's testcase, but I don't have anything special with python source lying around. ** Changed in: bash-completion (Ubunt

[Bug 660613] Re: COMP_WORDS bad array subscript in python completion

2013-04-05 Thread Nicolas Krzywinski
I just encountered this on my server, which is debian with bash 4.1.5(1)-release, python 2.6.6 and kernel 2.6.32-5-amd64 But it works with calling the python cmd only: python /etc/bash_completion.d/ Exploit: /usr/bin/python /etc/ba-bash: COMP_WORDS: Falscher Feldbezeichner. sh Notice: it does no

[Bug 660613] Re: COMP_WORDS bad array subscript in python completion

2013-04-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bash-completion (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/660613 Titl

[Bug 660613] Re: COMP_WORDS bad array subscript in python completion

2011-01-04 Thread Michael Foord
I have this problem when trying to use bash completion with a buildout python. The following is sufficient to trigger it: bin/python -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/660613 Title:

[Bug 660613] Re: COMP_WORDS bad array subscript in python completion

2010-10-18 Thread Jacob Wan
I noticed this problem too. One bit of information to add: it seems to only happen when the python executable is being invoked via a symbolic link. For example, if I want to run the script app.py in the current directory, "/usr/bin/python a" causes the error, while "/usr/bin/python2.6 a" does not