From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-29145-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 1652 invoked by alias); 4 May 2011 00:40:09 -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: 29145
Received: (qmail 28039 invoked from network); 4 May 2011 00:40:06 -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=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE
	autolearn=ham version=3.3.1
Received-SPF: none (ns1.primenet.com.au: domain at closedmail.com does not designate permitted sender hosts)
From: Bart Schaefer <schaefer@brasslantern.com>
Message-id: <110503173950.ZM16589@torch.brasslantern.com>
Date: Tue, 03 May 2011 17:39:50 -0700
In-reply-to: <BANLkTim9YUZh8YMfvFxWqJnHHC6UtMaLag@mail.gmail.com>
Comments: In reply to Felipe Contreras <felipe.contreras@gmail.com>
 "Re: zle messes up 'words' variable?" (May  3,  8:41pm)
References: <BANLkTik3BGrNd389-cDELWwdqR_LZ-qgOA@mail.gmail.com>
	<BANLkTinGAGOPj52wRq1yjpyJtmSuZhMCmQ@mail.gmail.com>
	<110428203139.ZM11856@torch.brasslantern.com>
	<BANLkTin1YcDOSGb+9FGYVgoC4cwN37_dnA@mail.gmail.com>
	<110502184235.ZM14465@torch.brasslantern.com>
	<BANLkTiktPbzZ4v=NSNkP5CV78ctSTQ9gsg@mail.gmail.com>
	<110503073902.ZM15889@torch.brasslantern.com>
	<110503080432.ZM15979@torch.brasslantern.com>
	<BANLkTim9YUZh8YMfvFxWqJnHHC6UtMaLag@mail.gmail.com>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: Felipe Contreras <felipe.contreras@gmail.com>
Subject: Re: zle messes up 'words' variable?
Cc: zsh-workers@zsh.org
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii

On May 3,  8:41pm, Felipe Contreras wrote:
}
} Part b is how to workaround the issue in the current versions of zsh,
} which is what the git guys are trying to do:
} http://article.gmane.org/gmane.comp.version-control.git/172371
} 
} I guess simply setting 'typeset -h words' on the top-level function
} (_git) should do the trick.

Yes, that should do it; but as zsh already has its own version of
completion for git, I'm surprised that anyone is encountering the
problem with the bash completion.  In fact that's probably why the
confusion over "words" didn't come to our attention before this.