Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Fix a typo in _git.
- X-seq: zsh-workers 25476
- From: "Mikael Magnusson" <mikachu@xxxxxxxxx>
- To: zsh-workers <zsh-workers@xxxxxxxxxx>
- Subject: Re: Fix a typo in _git.
- Date: Mon, 18 Aug 2008 11:47:54 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gmail.com; s=gamma;        h=domainkey-signature:received:received:message-id:date:from:to         :subject:in-reply-to:mime-version:content-type         :content-transfer-encoding:content-disposition:references;        bh=+MIbaFj/GVFZB9Sr9kdpmGyJjFgHRUxw3q9ujsvFxZo=;        b=lyKn80vkuNuS7fvlbQ0bDvBjtKcAiF6YrqEGBrr+XFu52nxFs3vr20M2jh3A5ElFMk         jvKAB5hF33nzd1on3mLjarcTi8om7m2UKqslqNby7wD8LTayfTnZ02o50w2wRh+44Oof         WzUx5hOd3rvQx8f9bEWtlyZb+YtaDTbwDn9ko=
- Domainkey-signature: a=rsa-sha1; c=nofws;        d=gmail.com; s=gamma;        h=message-id:date:from:to:subject:in-reply-to:mime-version         :content-type:content-transfer-encoding:content-disposition         :references;        b=aSyQsQc9E7rJkB95J6q7EOT9peICtUTPKLz4GKzB3dCq4IDUCCs3jxmUKvr3bf8GxT         FLTCZEjLqv0llSdYpGepxzsTu2vzcScNeLTbCTH5dWRlCwELyBTh37KGua3vMBh+v35F         QE37Syifg5OktRiDdluJWt6u/7i/ITrAfps5g=
- In-reply-to: <20080818014613.GA30193@xxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <237967ef0808151656j7787f169g4b3456910e05bfc2@xxxxxxxxxxxxxx>	 <20080817171321.GA24334@xxxxxxxx>	 <237967ef0808171027t4773ff36nb1cfe08942b63a5f@xxxxxxxxxxxxxx>	 <20080818014613.GA30193@xxxxxxxx>
2008/8/18 Clint Adams <clint@xxxxxxx>:
> On Sun, Aug 17, 2008 at 07:27:31PM +0200, Mikael Magnusson wrote:
>> git branch is a UI command, it's not guaranteed to always indicate the current
>> branch with a * for example. It also doesn't tell you if a branch is
>> in refs/heads
>> or refs/remotes. The completion doesn't differentiate between those yet, but
>> it definitely should, I don't think I'll be able to fix that though.
>>
>> As for _call_program, I don't really know what the purpose of that is. I don't
>> have a reason for not using it though.
>
>       _call_program tag string ...
>              This function provides a mechanism for the user to over‐
>              ride  the  use  of an external command.  It looks up the
>              command style with the supplied tag.  If  the  style  is
>              set,  its  value is used as the command to execute.  The
>              strings from the call  to  _call_program,  or  from  the
>              style  if set, are concatenated with spaces between them
>              and the resulting string is evaluated.  The return  sta‐
>              tus is the return status of the command called.
Ah, I see.
>> You have the same broken reply-to as the other guy, which means you
>> won't be in the to: field, and i have to remove myself manually each
>> time.
>> Either that, or gmail is doing something non-standard.
>
> You might mean Mail-Followup-To.
Okay, so it was gmail's fault then. It shows it as reply-to in the UI,
but when I click show original, i see it's mail-followup-to. I'll
admit I don't know everything there is to know about email headers,
and I'm sorry for falsely accusing you of doing something wrong :).
-- 
Mikael Magnusson
Messages sorted by:
Reverse Date,
Date,
Thread,
Author