Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: nits with new _git
- X-seq: zsh-workers 29303
- From: Nikolai Weibull <now@xxxxxxxx>
- To: Mikael Magnusson <mikachu@xxxxxxxxx>
- Subject: Re: nits with new _git
- Date: Tue, 17 May 2011 14:56:50 +0200
- Cc: zsh workers <zsh-workers@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=vVx4T61sBHawOtty7S86Q1IkJBHMb2VXl0563xHU//I=; b=A8ZkVBBzOq7IUCW7y7lEWqsopOdiNGjIAsY0nt5DAJXtJMC3+FrkKxQIw0y0Dc0tvD /6c+nzI/cnZWYpIa/DrbVcFjdsjtOgOIPG/iWp/cgjq72mHjKHkPnoO/ls8oJ2gcqpZ/ cM+x1qVCwzuWLM+i2j3K6UcGzDtMD9vuGDES4=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=dWBv8iG5WvwxvCM743lGrgXTQI+HyDvtKm8NF6ii1TP3PdABYXKkY5PN1njYl+umzu iiTUJU69UuOi24DPqswuuEENcz1yvAXZWQX0mCW5BZgXhLjLn2xslKL6FU/i8xyJsdGh 2UVlKZmxDjltqAd5eLs14OONgadv8VPUyYnEY=
- In-reply-to: <BANLkTinV2euaa_w+F7m7U0KMZm1ajYDMUg@mail.gmail.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <BANLkTinV2euaa_w+F7m7U0KMZm1ajYDMUg@mail.gmail.com>
- Sender: nikolai.weibull@xxxxxxxxx
On Sat, May 14, 2011 at 03:28, Mikael Magnusson <mikachu@xxxxxxxxx> wrote:
> 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.
I can’t reproduce this issue.
> The other thing is that git branch -d -r <tab> doesn't complete remote branches.
Yes, this is still on the TODO list.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author