zsh-workers
 help / color / mirror / code / Atom feed
From: Clint Adams <clint@zsh.org>
To: zsh-workers <zsh-workers@sunsite.dk>
Subject: Re: Fix a typo in _git.
Date: Tue, 19 Aug 2008 01:41:47 +0000	[thread overview]
Message-ID: <20080819014147.GA14537@scru.org> (raw)
In-Reply-To: <237967ef0808151656j7787f169g4b3456910e05bfc2@mail.gmail.com>

On Sat, Aug 16, 2008 at 01:56:36AM +0200, Mikael Magnusson wrote:
> http://git.mika.l3ib.org/?p=zsh-cvs.git;a=history;f=Completion/Unix/Command/_git;h=mika


From: Mikael Magnusson <mikachu@gmail.com>
Date: Tue, 19 Aug 2008 01:10:13 +0000 (+0200)
Subject: Complete revs and files after `git bisect start`.
X-Git-Url: http://git.mika.l3ib.org:1234/?p=zsh-cvs.git;a=commitdiff_plain;h=f2886ca3b3180c9327784b90ab3fcb56c554a8a5

Complete revs and files after `git bisect start`.

I'm using _files here since the bisection works across a range of commits
that might have different paths in them anyway, and I think gathering
all paths across the whole range is just masochistic and very slow,
so might as well use the ones from the working dir.

The -- is optional so technically the second _arguments could have an
_alternative that also adds _files, but I think that would just make
the completion messier for little value.
---

diff --git a/Completion/Unix/Command/_git b/Completion/Unix/Command/_git
index 0e2efab..468ce14 100644
--- a/Completion/Unix/Command/_git
+++ b/Completion/Unix/Command/_git
@@ -1464,6 +1464,16 @@ _git-bisect () {
         _arguments \
           '*::arguments: _normal' && ret=0
         ;;
+      (start)
+        if (( words[(I)--] < CURRENT && words[(I)--] > 0 )); then
+          _arguments \
+            '*:paths:_files' && ret=0
+        else
+          _arguments \
+            '2:bad revision:__git_commits' \
+            '*:good revision:__git_commits' && ret=0
+        fi
+        ;;
 
       (*)
         _nothing


  parent reply	other threads:[~2008-08-19  1:42 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-15 23:56 Mikael Magnusson
2008-08-16  0:45 ` Clint Adams
2008-08-16 12:56 ` Clint Adams
2008-08-16 13:25 ` Clint Adams
2008-08-16 13:55 ` Clint Adams
2008-08-16 16:15 ` Clint Adams
2008-08-16 17:59 ` Clint Adams
2008-08-16 18:29 ` Clint Adams
2008-08-17 14:03 ` Clint Adams
2008-08-17 17:13 ` Clint Adams
2008-08-17 17:27   ` Mikael Magnusson
2008-08-18  1:46     ` Clint Adams
2008-08-18  9:47       ` Mikael Magnusson
2008-08-18 20:10         ` Mikael Magnusson
2008-08-18 22:45           ` Clint Adams
2008-08-19  0:09             ` Mikael Magnusson
2008-08-19  0:25               ` Clint Adams
2008-08-19  0:37                 ` Mikael Magnusson
2008-08-19  0:39                   ` Mikael Magnusson
2008-08-19  0:58                   ` Clint Adams
2008-08-19  1:05                   ` Clint Adams
2008-08-17 23:23 ` Mikael Magnusson
2008-08-17 23:30   ` Mikael Magnusson
2008-08-18  0:08     ` Phil Pennock
2008-08-19  1:08 ` Clint Adams
2008-08-19  1:41 ` Clint Adams [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-10-18 21:23 Mikael Magnusson

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=20080819014147.GA14537@scru.org \
    --to=clint@zsh.org \
    --cc=zsh-workers@sunsite.dk \
    /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).