git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Fix git-completion.bash for use in zsh

From
AMAlex Merry <kde@randomguy3.me.uk>
Date
Mar 20, 2012, 11:53 UTC
Message-ID
<4F686FA2.8070803@randomguy3.me.uk>
In-Reply-To
<4E5F8CF3.3060304@randomguy3.me.uk>

This is just a reminder message, since I haven't heard anything back on this, and it hasn't made its way into the repo.

I realise Felipe Contreras has been pushing a different approach to making it work properly in zsh, but this should be a fairly innocuous fix in the meantime.

Alex
On 01/09/11 14:47, Alex Merry wrote:
Show 26 quoted lines
> Certain versions (or option combinations) of zsh appear to treat
> things like
> local some_var=()
> as a function declaration.  This makes errors appear when using it in
> combination with the GIT_PS1_SHOWUPSTREAM option.
>
> Signed-off-by: Alex Merry<dev@randomguy3.me.uk>
> ---
>   contrib/completion/git-completion.bash |    3 ++-
>   1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
> index 5a83090..89de45d 100755
> --- a/contrib/completion/git-completion.bash
> +++ b/contrib/completion/git-completion.bash
> @@ -106,8 +106,9 @@ __gitdir ()
>   __git_ps1_show_upstream ()
>   {
>          local key value
> -       local svn_remote=() svn_url_pattern count n
> +       local svn_remote svn_url_pattern count n
>          local upstream=git legacy="" verbose=""
> +       svn_remote=()
>
>          # get some config options from git-config
>          while read key value; do
Previous: Alex MerryNext: Junio C Hamano
Message 2 of 4 in “Fix git-completion.bash for use in zsh”
  1. Fix git-completion.bash for use in zshAlex Merry, Sep 1, 2011
  2. Alex MerryMar 20, 2012
  3. Junio C HamanoMar 20, 2012
  4. Junio C HamanoMar 20, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.