On Sunday, July 7, 2024 10:47 AM, Doron Behar wrote: >They don't perform any version checks as far as I can see in their implementation. > >Almost all commands that the ZSH team maintains completions for, don't perform >version checks and the maintainers of the commands themselves don't bother >taking responsibility for that and usually users don't complain. If a ZSH user notices >a new command or new option missing from such a completion function, they can >submit a patch to the ZSH project, and setup a workaround until there is a new ZSH >release with their patch included. > >Besides the option of living with this potential version mismatch imperfection, you >could also ask the ZSH team to remove their implementation and start maintain >their implementation here. However, they might object because not all distributions >will accommodate to this change in both projects... > >I personally think that Git is a stable enough project that the commands and >options don't deviate enough between the different versions of it, So it'd be easier >for you and for the distributions if you'd let go of your implementation. > >On Sun, Jul 07, 2024 at 04:15:53PM +0200, Andreas Schwab wrote: >> On Jul 07 2024, Doron Behar wrote: >> >> > ZSH completion is almost always distributed with every distribution >> > of ZSH, so there is no need for the two projects to maintain two >> > completion functions for the same program :). >> >> How do they keep it in sync with the particular version of git >> installed in the system? >> >> -- >> Andreas Schwab, schwab@xxxxxxxxxxxxxx >> GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA >> AEC1 "And now for something completely different." >> There are frequent updates to the git CLI. Freezing ZSH completion at an older version may not be useful. If there is a version compatibility error during install, perhaps take this up with rpm or apt depending on your package manager. I am curious as to why ZSH is overriding git completions.
