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 bash_completion.
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 from bash_completion or also debug bash_completion selectively.
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 bash_completion.
So I propose to set -v or set +v based on the value of $BASH_COMPLETIO N_DEBUG, but restore the original setting at the end of the script.
This will make it possible to debug without being overwhelmed by output from bash_completion or also debug bash_completion selectively.
What do you think?
A version that does this can be found here: git.zoopnet. de/bash- completion. git?a=blob_ plain;f= bash_completion ;hb=601bb9cdd81 0467b5ce2c4a2c6 72f68ba4b43e55
http://
Let me know whether this works for you.