Re: Zsh completion with rubber triggers an error message

Le 3 sept. 2026 à 17:53, Oliver Kiddle <opk@xxxxxxx> a écrit :

Normally, where a completion is added to a project's own repository, we
remove it from zsh. So I would instead suggest that the few commits it
has received on the zsh side be merged into rubber's official repository
and we remove it from zsh. There aren't too many changes, just a typo
fix and addition of (-.) to a file glob. Is that something you could
handle or should I create a PR?

Thanks

Oliver

I can take care of it.

However, just to make things clear, let me mention that the completion file had been added to the project repository *before* it was added to zsh. Indeed:

* it was introduced in their repository on 2005-04-15 as `data/_rubber` (commit fcda33f130b14515f502e3e07e16d2e08552d2ed - Added Zsh completion function.)

* updated on 2005-07-03 (commit 54cbc720b593eb84c425e27b84080a1a25d20639 - Documentation updates)

* and again on 2005-07-12 (commit e84bcbc57f3e6de185cfa9ece325965c0f85dab1 - Added module list detection to Zsh completion.)

The latter corresponds to the version initially introduced in zsh repository (the very same day).

A practical question: the current situation (the completion file being handled by the zsh developers) makes the completion file automatically installed when a user installs zsh, would they have or not rubber installed. If it is removed from zsh and now fully handled by the rubber developers, I guess that it means they also have to take care of installing the completion file somewhere when rubber is installed by some user, right?

Can you point me to some documentation on how this should be done, so that I could mention it in my PR (I am not sure that rubber developers be really familiar with how to install zsh completion rules: this might even be the reason why the file has been handled by zsh in the first place, even though they had the completion file in their repository).

Thanks.

Sylvain