[Bash-completion-devel] Bash completion not being sourced

Kip Warner kip at thevertigo.com
Wed Jun 8 05:29:22 UTC 2016

On Tue, 2016-06-07 at 22:25 -0700, Kip Warner wrote:
> Hey list,
> My Debianianized package ships the following bash completion file:
>     /usr/share/bash-completion/completions/mypackage-completion
> The file does not appear to be automatically sourced upon a shell
> login
> unless done so manually...
>     $ . /usr/share/bash-completion/completions/mypackage-completion
>     $ mypackage --[TAB]
> Tab completion then works. I've tried setting the executable bit on
> the
> file, but it doesn't seem to make any difference. Is there some kind
> of
> postinst hook my package needs to run?
> Regards,

*sigh* I just figured it out. mypackage-completion should be just
mypackage in order to get bash completion to work.

Kip Warner -- Senior Software Engineer
OpenPGP encrypted/signed mail preferred

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/bash-completion-devel/attachments/20160607/43e21ba2/attachment.sig>

More information about the Bash-completion-devel mailing list