From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26186 invoked by alias); 8 Oct 2015 03:50:17 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 20706 Received: (qmail 26991 invoked from network); 8 Oct 2015 03:50:16 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version:content-type; bh=mX8Xp6QTGsaIxwfvyHHIAGO5M6BIHyKqMUAkBwZz82Q=; b=icGnY/+vNi5fwjji4mFW8QpcOXyQYV3+mFz8iENO3GA8SvvrRITarqbDUPWpVhrDIi NYbWzGvqg73HdS1EqNoDnGMBEcle1hQ+JUoZu6McI77yXGRsuuLSTgFLNS5w5KTewE1U j4SnhO/ZNBdTd6vL/xWUVZ5FB3/bwlxtnmE9VY69BBYcrQEeL97IutxVt4YVrREMXRWS GXVkU5ge08bkQfqC0Yclnbph/N4aIg1lrlQJ0tICj/hrz4mf8cLtvhT19BwrkTMP8dHp 9ft9IjK/vYppk7BDG2rhKdeO4cmiHTxClnsUchZBmKrsDM9uUjIG8TJy2abkpmj0gx88 ZrfA== X-Gm-Message-State: ALoCoQkW61/7/SK6z2uMzHBd9e4P3TSanHYkJ/VGLze6g3TgsEYiAC68hEJjBmWsiCsD6hktOInQ X-Received: by 10.202.97.196 with SMTP id v187mr2886745oib.91.1444276214321; Wed, 07 Oct 2015 20:50:14 -0700 (PDT) From: Bart Schaefer Message-Id: <151007205011.ZM3230@torch.brasslantern.com> Date: Wed, 7 Oct 2015 20:50:11 -0700 In-Reply-To: <28911.1444256551@thecus.kiddle.eu> Comments: In reply to Oliver Kiddle "Re: tag-order with git refs" (Oct 8, 12:22am) References: <20151007120820.6f8a59e9@pwslap01u.europe.root.pri> <28911.1444256551@thecus.kiddle.eu> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: "Zsh Users' List" Subject: Re: tag-order with git refs MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Oct 8, 12:22am, Oliver Kiddle wrote: > Subject: Re: tag-order with git refs > > It also doesn't help that in a couple of cases functions are called > sequentially instead of using _alternative. The following patch helps a > tiny bit with this. > > (( $+functions[__git_heads] )) || > __git_heads () { > - __git_heads_local > - __git_heads_remote > + _alternative \ > + 'heads-local::__git_heads_local' \ > + 'heads-remote::__git_heads_remote' > } I think this will also end up passing TAG:DESCR:ACT (with empty DESCR) down to _all_labels, which will take the "if" branch that adds the -J option to compadd to make the tag a group name. (time passes) And indeed the patch does accomplish that, so now there is a group named heads-local, but the style Peter thinks should work, still does not. On the other hand, the style Oliver suggested with the list of "all tags along the path" does exactly what Peter wants. Oliver, can you explain why?