zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <opk@zsh.org>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Version of git vs. version of zsh completion for it
Date: Tue, 20 Apr 2021 22:48:25 +0200	[thread overview]
Message-ID: <49389-1618951705.200918@Ujb3.eI9Q.SdVO> (raw)
In-Reply-To: <CAH+w=7bG8Dfs2+nOJgaK0zx3zpf3q3aKF62hLaL8Fyyu133L1w@mail.gmail.com>

Bart Schaefer wrote:
> Just as an example:
>
> % git stash drop <TAB>
> _arguments:comparguments:325: invalid argument: _git-notes

That was fixed by dana in 754658aff3 (2020-03-13) having been caused by
me in 8aa84bd5fc / 44923 (2019-11-24). 5.8 falls between those, I'm
afraid.

> It would be OK if this just failed to complete, but spewing all those
> errors because Ubuntu hasn't released packages for the latest git
> seems unfriendly.

In this particular case that has nothing to do with it. It looks like I
accidentally pasted "_git-notes" into a random part of the file and
failed to notice.

> This is of course a generic problem with keeping supplied completions
> congruent with installed software,

By running the release version of zsh from a distribution, it should
hopefully be of at least approximately the same vintage as the rest
of the software. But more people running fresh builds gives us a chance
of finding errors of this sort before they hit a release.

Option updates in completions tend to be fairly error-prone and I've
been responsible for one or other error in most releases. I've not
updated _git for options since 2.24 so your next Ubuntu upgrade will
potentially give you a newer git than we complete for.

Oliver


      reply	other threads:[~2021-04-20 20:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20 19:55 Bart Schaefer
2021-04-20 20:48 ` Oliver Kiddle [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49389-1618951705.200918@Ujb3.eI9Q.SdVO \
    --to=opk@zsh.org \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).