On Tue, 08 Nov 2011 18:21:21 +0200 Ville Skyttä <ville.sky...@iki.fi> wrote:
> > Good. Can I push this variant to the master branch? > > Sure, go ahead. > > But I've run into something not nice at all (and not at all related to > your changes): > > $ bash --norc > $ _foo() { echo -n completing foo ; } > $ _loader() { echo -n loading for $1; complete -F _foo $1; return 124; } > $ complete -D -F _loader > $ foo <TAB>loading for foocompleting foo > > So far, so good. But then: > > $ /etc/init.d/foo <TAB>completing foo > > So if completion for a basename foo is already installed, the default > completion loader no longer fires for /etc/init.d/foo -- the basename > completion is invoked directly instead. (It works ok the other way > around, i.e. if /etc/init.d/foo is completed first, then plain foo later.) > > I can't believe I missed this when testing various dynamic loading > scenarios. And I'm afraid this means that we'll need to load > completions for /etc/init.d and friends eagerly at bash_completion load > time after all :( I merged completions/service into bash_completion and pushed this to the master. -- Igor _______________________________________________ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/bash-completion-devel