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
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
It being the BASH_COMPLETION variable...
--
bash completion inhibits ability to debug login scripts
https://bugs.launchpad.net/bugs/205444
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.ubu
Actually, sourcing bash_completion twice is fine, since we only try to
set it if it's empty and we only mark it read-only after we've set it to
something.
So I'll just add the fix for the -v issue.
--
bash completion inhibits ability to debug login scripts
https://bugs.launchpad.net/bugs/205444
OK, sourcing bash_completion twice is another problem. I'll check this
in the evening and include the fix above in the next upload.
--
bash completion inhibits ability to debug login scripts
https://bugs.launchpad.net/bugs/205444
You received this bug notification because you are a member of Ubun
See also bug #149527 for what it's worth. I had forgotten that it
existed, although I had commented on it in the past.
--
bash completion inhibits ability to debug login scripts
https://bugs.launchpad.net/bugs/205444
You received this bug notification because you are a member of Ubuntu
Bugs, whi
If anything is pending on me, then I reaffirm that I think the fix looks
good. Perhaps you should check that you're not crossing paths with the
#149527 fix, though.
--
bash completion inhibits ability to debug login scripts
https://bugs.launchpad.net/bugs/205444
You received this bug notificatio
To test this bug, you could just put the script in your home directory
and instead of sourcing /etc/bash_completion source ~/bash_completion.
But if you agree with the general approach I'll include this in the next
upload.
** Changed in: bash-completion (Ubuntu)
Status: New => In Progress
On Sun, 23 Mar 2008 12:39:37 -, "Mika Fischer"
<[EMAIL PROTECTED]> said:
> So I propose to set -v or set +v based on the value of
> $BASH_COMPLETION_DEBUG, but restore the original setting at the end of
> the script.
>
> This will make it possible to debug without being overwhelmed by
> output
Thanks for reporting this bug in Ubuntu.
The main problem with the readonly variables has already been fixed in
hardy.
The issue with -v is a bit more tricky. I think the idea was that if you
set -v to debug your startup script, you're probably not interested in
thousands of lines of output from
** Changed in: bash-completion (Ubuntu)
Sourcepackagename: bash => bash-completion
Assignee: (unassigned) => Mika Fischer (zoop)
--
bash completion inhibits ability to debug login scripts
https://bugs.launchpad.net/bugs/205444
You received this bug notification because you are a member of Ub
The following quick patch attempts to solve two problems in the Gutsy
/etc/bash_completion:
* Don't "set -v" or "set +v" if it's already set
* If BASH_COMPLETION or BASH_COMPLETION_DIR are declared readonly, don't even
attempt to modify them
The latter would (if my quick analysis isn't compl
Here's what the bash manual says about readonly assignments:
> If any of the assignments attempts to assign a value to a
> readonly variable, an error occurs, and the command exits with a non-
> zero status.
So I guess that's the root cause of this problem. I would interpr
13 matches
Mail list logo
