** Changed in: bash-completion (Ubuntu Karmic)
Status: New = Fix Released
--
no tab completion on path that contains a space
https://bugs.launchpad.net/bugs/419509
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I can't test karmic, but your unmount example works just fine on lucid.
** Changed in: bash-completion (Ubuntu)
Status: New = Fix Released
--
no tab completion on path that contains a space
https://bugs.launchpad.net/bugs/419509
You received this bug notification because you are a member
Nobody answer me?
--
no tab completion on path that contains a space
https://bugs.launchpad.net/bugs/419509
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: bash-completion (Ubuntu Karmic)
Status: Fix Released = New
--
no tab completion on path that contains a space
https://bugs.launchpad.net/bugs/419509
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I'm reopening this bug cause of I cannot complete sudo mount if label of
the usb key contains a space.
Step to reproduce:
Mount a key with a label lihke foo foo
type:
sudo umount /media/fooTAB
this command doesn't show
/media/foo\ foo
** Changed in: bash-completion (Ubuntu)
Status: Fix
Hmm, seems to be working now. Maybe I just had to log out and then log
back in or something. I thought opening a new terminal would be good
enough. At any rate, I'm glad to have my tab-completion back. :-)
--
no tab completion on path that contains a space
seems fixed for me. adam could you try making a new user account and see
if it affected?
--
no tab completion on path that contains a space
https://bugs.launchpad.net/bugs/419509
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Still broken in Karmic with the latest version of bash-completion. I
tried putting the file from comment #4 in /etc/bash_completion.d/ and
when I launched a new terminal it just hung and never got to a point
where I could enter any commands.
--
no tab completion on path that contains a space
Works for me, and I do have bash_completion installed and enabled in
.bashrc.
--
no tab completion on path that contains a space
https://bugs.launchpad.net/bugs/419509
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I am still seeing this in 1:1.0-3ubuntu2. I've taken bash_completion
out of my .bashrc to make shells usable again.
--
no tab completion on path that contains a space
https://bugs.launchpad.net/bugs/419509
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: bash-completion (Debian)
Status: Fix Committed = Fix Released
--
no tab completion on path that contains a space
https://bugs.launchpad.net/bugs/419509
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Branch linked: lp:ubuntu/bash-completion
--
no tab completion on path that contains a space
https://bugs.launchpad.net/bugs/419509
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Bug watch added: Debian Bug tracker #544024
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544024
** Also affects: bash-completion (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544024
Importance: Unknown
Status: Unknown
--
no tab completion on path that
** Changed in: bash-completion (Debian)
Status: Unknown = Fix Committed
--
no tab completion on path that contains a space
https://bugs.launchpad.net/bugs/419509
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This bug was fixed in the package bash-completion - 1:1.0-3ubuntu2
---
bash-completion (1:1.0-3ubuntu2) karmic; urgency=low
* Backport quote_readline fix for bash 4, since double-quoting for compgen
is no longer necessary (LP: #419509).
-- Colin Watson cjwat...@ubuntu.com
Odd...as I'm not seeing this problem at all on my Karmic install.
** Also affects: bash-completion (Ubuntu Karmic)
Importance: Undecided
Status: Confirmed
--
no tab completion on path that contains a space
https://bugs.launchpad.net/bugs/419509
You received this bug notification
Please update to Beta and verify this bug still exists.
** Changed in: bash-completion (Ubuntu Karmic)
Importance: Undecided = Low
** Changed in: bash-completion (Ubuntu Karmic)
Status: Confirmed = Incomplete
--
no tab completion on path that contains a space
On Fri, Oct 02, 2009 at 04:15:00PM -, Robbie Williamson wrote:
Please update to Beta and verify this bug still exists.
** Changed in: bash-completion (Ubuntu Karmic)
Importance: Undecided = Low
** Changed in: bash-completion (Ubuntu Karmic)
Status: Confirmed = Incomplete
yes, I can confirm it's still broken.
If I start bash without the bash-completion, it works:
$ bash --norc
bash-4.0$ ls Ubuntu\ One/TAB
060428-bagger288-garzweiler.jpg Shared With Me@
Pics/stats/
but if in that same shell I load in the completion,
i've experienced the same problem with #
$ less \#ubuntu-tabtab
#ubuntu-motu #ubuntu-server
$ less \#ubuntu-mtab --- nothing happens
I think the problem is that bash-completion isn't reading escaped
characters correctly.
--
no tab completion on path that contains a space
In Karmic, I am experiencing the same issue as described. I did not have
this issue before I upgraded from Jaunty to Karmic.
Munzir Taha's wonderful workaround works for me.
--
no tab completion on path that contains a space
https://bugs.launchpad.net/bugs/419509
You received this bug
Broken in Karmic here as well, seems to coincide with the introduction
of bash 4.
To get tab completion working again I used a relatively ancient version
of /etc/bash_completion (RELEASE: 20060301) in combination with the
existing /etc/bash_completion.d directory. This file (which comes from
an
I have the same bug also and just found if I used backslash before the command
it works. e.g
mun...@dv6:~$ \cat foo\ foo/TAB
works!
--
no tab completion on path that contains a space
https://bugs.launchpad.net/bugs/419509
You received this bug notification because you are a member of Ubuntu
Glad it's not just me, thought I was losing my mind or my tab key was
flaking out or something. .
--
no tab completion on path that contains a space
https://bugs.launchpad.net/bugs/419509
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
confirmed working fine in Jaunty, confirmed broken as described in
Karmic.
--
no tab completion on path that contains a space
https://bugs.launchpad.net/bugs/419509
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Changed in: bash-completion (Ubuntu)
Status: New = Confirmed
--
no tab completion on path that contains a space
https://bugs.launchpad.net/bugs/419509
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Tags added: regression-potential
** Tags removed: amd64
--
no tab completion on path that contains a space
https://bugs.launchpad.net/bugs/419509
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/30873512/Dependencies.txt
--
no tab completion on path that contains a space
https://bugs.launchpad.net/bugs/419509
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
28 matches
Mail list logo
