...Although even with extglob, this still seems to fail:
shopt -s failglob
mkdir test
cd test
vim
--
improper quoting in bash completion script
https://bugs.launchpad.net/bugs/194419
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Never mind, somehow extglob had gotten unset! (A changed default?)
--
improper quoting in bash completion script
https://bugs.launchpad.net/bugs/194419
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
Ah, crap. Just moved to hardy, and it's still broken.
shopt -s failglob
mkdir test
cd test
unzip
--
improper quoting in bash completion script
https://bugs.launchpad.net/bugs/194419
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
This bug was fixed in the package bash-completion - 20060301-3ubuntu2
---
bash-completion (20060301-3ubuntu2) hardy; urgency=low
* Bugfix release:
- Fix _get_cword more
- Fix _command function to correctly prune the command line (LP: #103395)
- Remove newline from options p
Thanks, I've fixed this problem too. I've not used your patch but fixed
it in a similar way that I fixed the original problem which should cover
some additional corner cases. It'll also be in the next upload.
--
improper quoting in bash completion script
https://bugs.launchpad.net/bugs/194419
You
I'm not using hardy yet, so I can't test (sorry), but I did just find
another similar bug:
mkdir test
cd test
touch [a].zip
touch a.zip
unzip
Patch attached.
** Attachment added: "bash_completion.patch"
http://launchpadlibrarian.net/13051516/bash_completion.patch
--
improper quoting in bas
I've prepared an updated package in my PPA which should fix the bug you
reported.
If you're using hardy I'd appreciate it if you could test it and report
whether your bug is indeed fixed and also whether you experienced any
other regressions.
You can get the package from here:
http://launchpadlib
** Changed in: bash-completion (Ubuntu)
Assignee: (unassigned) => Mika Fischer (zoop)
Status: Confirmed => In Progress
--
improper quoting in bash completion script
https://bugs.launchpad.net/bugs/194419
You received this bug notification because you are a member of Ubuntu
Bugs, which
This is a bug in the bash-completion package.
** Changed in: bash-completion (Ubuntu)
Sourcepackagename: bash => bash-completion
--
improper quoting in bash completion script
https://bugs.launchpad.net/bugs/194419
You received this bug notification because you are a member of Ubuntu
Bugs, which
I can confirm the initial author's report... Typing tar tf
does not offer me any items. The same is true for any other combination
of letters ending in an 'f' (i.e. tar ft works, tar
xf) does not. Deleting the file 'tgz' also solves the issue,
i.e. the problem does not occur with only the test.tar
This trivial patch for /etc/bash_completion fixes the tar issue:
2888c2888
< _filedir $ext
---
> _filedir "$ext"
However, I think I had another (similar) problem with failglob and
autocomplete for rm, but I cannot seem to reproduce that now.
--
improper quoting in bash completion scr
Fixing the quoting as in the patch above, fixes the initial issue (tar
autocompletion) for me.
--
improper quoting in bash completion script
https://bugs.launchpad.net/bugs/194419
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
I can confirm now. After sourcing the /etc/bash_completion file (.
/etc/bash_completion), I get the same behavior as was originally reported by
adw.
On Fri, Feb 22, 2008 at 3:51 PM, adw <[EMAIL PROTECTED]> wrote:
> Jim, chills42,
>
> It shouldn't complete to tgz at all, so I think you don't hav
Jim, chills42,
It shouldn't complete to tgz at all, so I think you don't have programmable
complete enabled.
Try running this line before testing:
. /etc/bash_completion
And it shouldn't complete without the space, I think. It would be
expecting more options instead of a filename.
--
improper
I was also unable to confirm the original reports steps. I am able to
confirm Jim J's reply.
tar tf
does not offer any items, however:
tar tf does offer items for completion as expected.
--
improper quoting in bash completion script
https://bugs.launchpad.net/bugs/194419
You received this bug
I couldn't confirm this on my Gutsy installation.
I used the same steps that adw used, but hitting after
tar tf
autocompleted a "t" and hitting again gave me tgz and test.tar as
the completion options.
So I typed
mkdir test
cd test
touch test.tar
touch tgz
tar tf
and I got expected behavior
Ok, I managed to reproduce the rm problem. In fact, this seems to affect
all file autocompletes:
mkdir test
cd test
touch [a]
touch a
ls
Should: do nothing, list both files as completion options on a second
Instead: autocompletes to a
(Again, it breaks autocomplete with failglob even without t
17 matches
Mail list logo
