Programmable completion bugs very often get reported in the wrong place. Most users aren't aware of how exactly it happens under the hood. Also, some packages do ship custom completions for the commands they provide.
In this case, dd completion is dynamically loaded from /usr/share/bash-completion/completions/dd, a file maintained by the bash-completion package. $ complete -p dd complete -o nospace -F _dd dd Usually un-reproducible broken-behaviour reports come from people with old cruft in /etc/bash_completion.d. Every file in there is sourced when the main bash-completion script loads. Old acroread packages were notable for re-defining bash-completion standard functions in a way that broke things. So, David, check everything in /etc/bash_completion.d to make sure apt thinks it SHOULD be there, or that you put it there yourself. e.g. on my system $ dpkg -S /etc/bash_completion.d/* > /dev/null dpkg-query: no path found matching pattern /etc/bash_completion.d/dput.dpkg-old dpkg-query: no path found matching pattern /etc/bash_completion.d/git.dpkg-old found files get printed on stdout, hence the redirect. -- #define X(x,y) x##y Peter Cordes ; e-mail: X(peter@cor , des.ca) "The gods confound the man who first found out how to distinguish the hours! Confound him, too, who in this place set up a sundial, to cut and hack my day so wretchedly into small pieces!" -- Plautus, 200 BC _______________________________________________ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/bash-completion-devel
