Jonathan Nieder wrote: > 1. bash-completion versions before 1.1 are broken by bash 4. > > 2. All known versions of git's completion script are broken by bash 4. > There is a patch cooking on the git mailing list to get it working > again. > > 3. Other completion scripts might need changes, too. There are about > 74 packages to check :(
Oops, forgot to include references. bash list --------- * Some quoting issue led to the splitting of _get_cword: http://thread.gmane.org/gmane.comp.shells.bash.bugs/13440 * The advertised behavior change (a new default for COMP_WORDBREAKS includes '='): http://thread.gmane.org/gmane.comp.shells.bash.bugs/15035 * The git log --pretty=<tab><tab> bug: http://thread.gmane.org/gmane.comp.shells.bash.bugs/14046 git list -------- * report that completion broke. COMP_WORKBREAKS already included '='... http://thread.gmane.org/gmane.comp.version-control.git/159448/focus=159481 * triage. http://thread.gmane.org/gmane.comp.version-control.git/159516/focus=159628 * first revision of patch. http://thread.gmane.org/gmane.comp.version-control.git/159991 * second revision of patch. http://thread.gmane.org/gmane.comp.version-control.git/160103 Upshot of the git discussion: | This ${COMP_WORDS[COMP_CWORD]} | construct apparently is not the right way to find the word to complete | anymore, assuming you want your completion script to work with bash 4 | and 3 as well. Unfortunately, we use this construct all over the | place. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
