From: Thomas Gummerer <t.gummerer@gmail.com>
To: "SZEDER Gábor" <szeder@ira.uka.de>
Cc: git@vger.kernel.org, felipe.contreras@gmail.com, gitster@pobox.com
Subject: Re: [PATCH] prompt: fix show upstream with svn and zsh
Date: Wed, 22 May 2013 09:32:44 +0200 [thread overview]
Message-ID: <87a9nn31wj.fsf@gmail.com> (raw)
In-Reply-To: <20130521224119.GF30969@goldbirke>
SZEDER Gábor <szeder@ira.uka.de> writes:
> Hi,
>
>
> On Tue, May 21, 2013 at 10:54:27PM +0200, Thomas Gummerer wrote:
>> Currently the __git_ps1 git prompt gives the following error with a
>> repository converted by git-svn, when used with zsh:
>>
>> __git_ps1_show_upstream:19: bad pattern: svn_remote[
>>
>> This was introduced by 6d158cba (bash completion: Support "divergence
>> from upstream" messages in __git_ps1), when the script was for bash
>> only. Make it compatible with zsh.
>
> What is the actual cause of this problem/incompatibility and how/why do
> these changes fix it?
>
>> - svn_remote[ $((${#svn_remote[@]} + 1)) ]="$value"
>> + svn_remote[$((${#svn_remote[@]} + 1))]="$value"
>
> I mean, did zsh really complained because of the space after the '[' ?!
Yes, removing the spaces after the '[' fixes the problem. I'm not very
proficient in shell scripting, so I can't tell if there is another
cause.
>> @@ -146,8 +146,8 @@ __git_ps1_show_upstream ()
>> svn*)
>> # get the upstream from the "git-svn-id: ..." in a commit message
>> # (git-svn uses essentially the same procedure internally)
>> - local svn_upstream=($(git log --first-parent -1 \
>> - --grep="^git-svn-id: \(${svn_url_pattern#??}\)" 2>/dev/null))
>> + set -a svn_upstream "$(git log --first-parent -1 \
>> + --grep="^git-svn-id: \(${svn_url_pattern#??}\)" 2>/dev/null)"
>> if [[ 0 -ne ${#svn_upstream[@]} ]]; then
>> svn_upstream=${svn_upstream[ ${#svn_upstream[@]} - 2 ]}
>
> If so, then what about this one?
You're right, this line gives an error too, the code just wasn't
following that path before. I'll fix it in the re-roll. Other than
those two I couldn't spot any other occurrence of this pattern.
> Best,
> Gábor
Thanks,
Thomas
next prev parent reply other threads:[~2013-05-22 7:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 20:54 [PATCH] prompt: fix show upstream with svn and zsh Thomas Gummerer
2013-05-21 22:41 ` SZEDER Gábor
2013-05-21 23:04 ` Felipe Contreras
2013-05-21 23:36 ` SZEDER Gábor
2013-05-22 0:03 ` Felipe Contreras
2013-05-22 0:20 ` SZEDER Gábor
2013-05-22 0:29 ` Felipe Contreras
2013-05-22 0:44 ` SZEDER Gábor
2013-05-22 7:32 ` Thomas Gummerer [this message]
2013-05-28 10:30 ` SZEDER Gábor
2013-05-22 3:13 ` Felipe Contreras
2013-05-22 7:36 ` Thomas Gummerer
2013-05-22 7:40 ` [PATCH v2] " Thomas Gummerer
2013-05-22 7:56 ` Felipe Contreras
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=87a9nn31wj.fsf@gmail.com \
--to=t.gummerer@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=szeder@ira.uka.de \
/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.
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).