On Sun, Apr 8, 2018 at 11:26 AM, Florian Gamböck <mail@xxxxxxxx> wrote: > Adding external subcommands to Git is as easy as to put an executable > file git-foo into PATH. Packaging such subcommands for a Linux > distribution can be achieved by unpacking the executable into /usr/bin > of the user's system. Adding system-wide completion scripts for new > subcommands, however, can be a bit tricky. > > Since bash-completion started to use dynamical loading of completion > scripts somewhere around v2.0, it is no longer sufficient to drop a > completion script of a subcommand into the standard completions path, > /usr/share/bash-completion/completions, since this script will not be > loaded if called as a git subcommand. Also v1.90 here? (hint from the cover letter, please be exact) If Gits own completion script would be broken up by subcommand, would that also deliver an improvement in performance? Thanks, Stefan
