@Mike Doherty, Victor Zamanian: Just checked out bash_completion. If you use the master branch (dangerous?) it's fixed, but it's not fixed at the 1.2 tag. I was looking for the specific commit that fixed it, but I gave up.
Nobody seems to be prepping for a release yet, although the time between releases seems to be about 6-9 months, and it's been 6 months since 1.2. So it may be coming in the next several months. If you must have it, and you just want instructions, do the following:
@Mike Doherty, Victor Zamanian: Just checked out bash_completion. If you use the master branch (dangerous?) it's fixed, but it's not fixed at the 1.2 tag. I was looking for the specific commit that fixed it, but I gave up.
git clone git://git. debian. org/git/ bash-completion /bash-completio n.git
Nobody seems to be prepping for a release yet, although the time between releases seems to be about 6-9 months, and it's been 6 months since 1.2. So it may be coming in the next several months. If you must have it, and you just want instructions, do the following:
git clone git://git. debian. org/git/ bash-completion /bash-completio n.git
cd bash-completion
git checkout master
sudo cp bash-completion /etc
Then add to your .bashrc, .profile, .bash_profile, whatever:
# Use bash-completion, if available completion ]; then completion
if [ -f /etc/bash_
. /etc/bash_
fi
For fun, notice the message attached to SHA 0c4db6eb969892c a282e7d5c8a524f 2c062eb42e. That just made my day.