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 address hidden> wrote:
> 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 quoting in bash completion script
> https://bugs.launchpad.net/bugs/194419
> You received this bug notification because you are a direct subscriber
> of the bug.
>
I can confirm now. After sourcing the /etc/bash_ completion file (. completion) , I get the same behavior as was originally reported by
/etc/bash_
adw.
On Fri, Feb 22, 2008 at 3:51 PM, adw <email address hidden> wrote:
> Jim, chills42, completion /bugs.launchpad .net/bugs/ 194419
>
> 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_
>
> And it shouldn't complete without the space, I think. It would be
> expecting more options instead of a filename.
>
> --
> improper quoting in bash completion script
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>