[Bug 219406] Re: bash autocomplete broken when a : is in the path

2015-08-29 Thread Mathew Hodson
** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/219406 Title: bash autocomplete broken when a : is in the path To manage notifications about this bug go to: https://bugs.launchp

[Bug 219406] Re: bash autocomplete broken when a : is in the path

2014-11-28 Thread Peter Cordes
further update: comments for __ltrim_colon_completions() in /usr/share /bash-completion/bash_completion say you can # Remove colon (:) from list of word completion separators #COMP_WORDBREAKS=${COMP_WORDBREAKS//:} in your .bashrc

[Bug 219406] Re: bash autocomplete broken when a : is in the path

2014-11-28 Thread Peter Cordes
Apparently this is a known problem that can't be fixed. /usr/share/doc /bash-completion/README.gz FAQ says: Q. Completion goes awry when I try to complete on something that contains a colon. A. This is actually a 'feature' of bash. bash recognises a colon as starting a new completion token

[Bug 219406] Re: bash autocomplete broken when a : is in the path

2014-11-28 Thread Peter Cordes
/usr/share/bash-completion/bash_completion has a bunch of stuff about treating : specially, for completing host:path in scp and similar commands. Spent a bit of time looking at the source of this behaviour, but haven't found it yet. set -x before pressing tab, and paste that into a file to look

[Bug 219406] Re: bash autocomplete broken when a : is in the path

2014-11-13 Thread Rolf Leggewie
** Changed in: bash-completion (Ubuntu) Assignee: Rolf Leggewie (r0lf) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/219406 Title: bash autocomplete broken when a : is in the pa

[Bug 219406] Re: bash autocomplete broken when a : is in the path

2014-10-14 Thread Rolf Leggewie
Yes, indeed I was able to reproduce this now. ** Changed in: bash-completion (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/219406 Title: bash autocompl

[Bug 219406] Re: bash autocomplete broken when a : is in the path

2014-10-14 Thread Jarno Suni
I can reproduce in ubuntu 14.04 (trusty) Type the following in terminal and finally press Tabulator: cd /tmp && mkdir test && cd test && touch :test ls : Then the last line is: ls :\:test Press enter. ls: cannot access ::test: No such file or directory -- You received this bug notification bec

[Bug 219406] Re: bash autocomplete broken when a : is in the path

2014-10-13 Thread Rolf Leggewie
FWIW, I cannot reproduce this in trusty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/219406 Title: bash autocomplete broken when a : is in the path To manage notifications about this bug go to: h

[Bug 219406] Re: bash autocomplete broken when a : is in the path

2014-10-13 Thread Rolf Leggewie
does this ever occur in precise or later? ** Changed in: bash-completion (Ubuntu) Status: Triaged => Incomplete ** Changed in: bash-completion (Ubuntu) Assignee: (unassigned) => Rolf Leggewie (r0lf) -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 219406] Re: bash autocomplete broken when a : is in the path

2011-03-20 Thread Clint Byrum
I don't believe it is fixed. I'm using v 1.3 in natty, and its still not fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/219406 Title: bash autocomplete broken when a : is in the path -- ubun

[Bug 219406] Re: bash autocomplete broken when a : is in the path

2009-10-16 Thread Chris Jones
This appears to be fixed with bash-completion 1.1 (which is in sid) -- bash autocomplete broken when a : is in the path https://bugs.launchpad.net/bugs/219406 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list u

[Bug 219406] Re: bash autocomplete broken when a : is in the path

2009-03-10 Thread Bug Watch Updater
** Changed in: bash-completion (Debian) Status: Unknown => Won't Fix -- bash autocomplete broken when a : is in the path https://bugs.launchpad.net/bugs/219406 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailin

[Bug 219406] Re: bash autocomplete broken when a : is in the path

2009-01-07 Thread James Westby
** Bug watch added: Debian Bug tracker #377935 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377935 ** Also affects: bash-completion (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377935 Importance: Unknown Status: Unknown -- bash autocomplete broken when a : is

[Bug 219406] Re: bash autocomplete broken when a : is in the path

2009-01-05 Thread Mika Fischer
** Changed in: bash-completion (Ubuntu) Assignee: Mika Fischer (zoop) => (unassigned) -- bash autocomplete broken when a : is in the path https://bugs.launchpad.net/bugs/219406 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubu

[Bug 219406] Re: bash autocomplete broken when a : is in the path

2008-06-07 Thread Mika Fischer
** Changed in: bash-completion (Ubuntu) Importance: Undecided => Medium Status: Confirmed => Triaged -- bash autocomplete broken when a : is in the path https://bugs.launchpad.net/bugs/219406 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 219406] Re: bash autocomplete broken when a : is in the path

2008-04-24 Thread Mika Fischer
** Changed in: bash-completion (Ubuntu) Sourcepackagename: bash => bash-completion Assignee: (unassigned) => Mika Fischer (zoop) Status: New => Confirmed -- bash autocomplete broken when a : is in the path https://bugs.launchpad.net/bugs/219406 You received this bug notification becau