From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-29272-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 18994 invoked by alias); 14 May 2011 01:28:58 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 29272
Received: (qmail 2182 invoked from network); 14 May 2011 01:28:57 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW autolearn=ham
	version=3.3.1
Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.google.com designates 209.85.220.171 as permitted sender)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:date:message-id:subject:from:to
         :content-type;
        bh=98HSVDcGOaDcdxmK34/4WZJ5Nsv5tjlpQKBSfuzR//w=;
        b=kwg/dhHBiN+GfPdjXJe1pq76zrvi3v6KhkC2jKqb7GerHU97dEQntXecDTFXOSpSzc
         JxznIAUvuCsxV7NQCO78hE5VaBcR6HsoEhwX+j3O/t8fGQKZBTrSAFSrKF5jqYD2Yaeo
         aSmnN5R9pUAA6cp36LebEQB4CjAda2X8nHrbI=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=UzfwZIGC6i/5spn5j6R7LxqFRyKOzgzwA7WZVQfT084eXoB8olga7i4cHRiy6f1g04
         vfUUf8SfhR33BYf0zpkcZMHMpKLKkSrUgYJnXhTZH24I07YxhO7JPTfvl106CPCtpd6R
         hK34YCnZAOd6g2JK4kbjTRnoKDc4e8F2iywEA=
MIME-Version: 1.0
Date: Sat, 14 May 2011 03:28:53 +0200
Message-ID: <BANLkTinV2euaa_w+F7m7U0KMZm1ajYDMUg@mail.gmail.com>
Subject: nits with new _git
From: Mikael Magnusson <mikachu@gmail.com>
To: zsh workers <zsh-workers@zsh.org>
Content-Type: text/plain; charset=UTF-8

Now that pws fixed the crash, I'm updating to the new _git, so far
I've noticed these two things.

git log --pret<tab> goes into correction, same for git show.
% git log --pretty=
---- option
--pretty  -- pretty print commit messages
---- corrections (errors: 2)
--grep    -- limit commits to those with log messages matching the given pattern
--pretty  -- pretty print commit messages

Usually this would hint at some missing ret=0 somewhere, but I
couldn't find any. Unconditionally returning 0 from _git does 'fix' it
though, so it must be somewhere.

The other thing is that git branch -d -r <tab> doesn't complete remote branches.

-- 
Mikael Magnusson