Shipping autocomplete file upstream for KDE Connect?

Shipping autocomplete file upstream for KDE Connect?

[Matthijs Tijink]

Dear all,

We at KDE Connect are in the process of improving our zsh autocomplete file, 
and were thinking it might be easier to ship the file ourselves.

However, I initially submitted an autocomplete file to zsh some months ago, 
and that's already released. So, I've got a few questions and hope you can 
answer them:

What's your preferred way of shipping autocomplete files? With zsh or with the 
program itself? In case it's with the program itself, how should we proceed 
with adding/removing the completion file?

Thanks in advance!

Kind regards, Matthijs Tijink

PS: I'm not subscribe to the mailing list, so please keep me on CC.

Re: Shipping autocomplete file upstream for KDE Connect?

[Eric Cook]

On 3/25/19 2:57 PM, Matthijs Tijink wrote:

> What's your preferred way of shipping autocomplete files? With zsh or with the
> program itself? In case it's with the program itself, how should we proceed
> with adding/removing the completion file?
>

If the program in question changes more frequently than zsh releases new versions,
about once an year at its current pace or the community of the program is more
familiar with its development process than zsh's; it would most likely be better served
releasing it with the program itself. Dropping the completer somewhere in $fpath,
site-functions or in the world of debian, vendor-functions.

As far as removing the completer from zsh, just a patch deleting the file should do.
that being said, if you were to ship a completer in $fpath's site-functions or
vendor-functions it would most likely have higher precedence than the one ship with
zsh and just work.