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

Re: [PATCH] git-completion: workaround zsh COMPREPLY bug

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Jan 27, 2012, 16:33 UTC
Message-ID
<CAMP44s1hdFDfs=a-3XNCYpLUqGw4rq5spsO6qesvP5sp-A1fJw@mail.gmail.com>
In-Reply-To
<7v4nvi2kgq.fsf@alter.siamese.dyndns.org>
On Fri, Jan 27, 2012 at 12:00 AM, Junio C Hamano <gitster@pobox.com> wrote:
Show 17 quoted lines
> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
>> zsh adds a backslash (foo\ ) for each item in the COMPREPLY array if IFS
>> doesn't contain spaces. This issue has been reported[1], but there is no
>> solution yet.
>> ...
>> Once zsh is fixed, we should conditionally disable this workaround to
>> have the same benefits as bash users.
>>
>> [1] http://www.zsh.org/mla/workers/2012/msg00053.html
>> [2] http://zsh.git.sourceforge.net/git/gitweb.cgi?p=zsh/zsh;a=commitdiff;h=2e25dfb8fd38dbef0a306282ffab1d343ce3ad8d
>
> That 2e25dfb8 only says:
>
>    Rocky Bernstein: 29135 (plus tweaks): compgen -W in bash completion
>
> without any explanation, which is not very useful.
Yeah, they development practices leaves a lot to be desired.
> Do you have a bug tracker ID or something for [1] above, with which I can
> amend the patch as Matthieu suggests?
I don't think there's something like that, but here's the original discussion:
http://thread.gmane.org/gmane.comp.shells.zsh.devel/22541
-- 
Felipe Contreras
Previous: Junio C Hamano
Message 7 of 7 in “git-completion: workaround zsh COMPREPLY bug”
  1. git-completion: workaround zsh COMPREPLY bugFelipe Contreras, Jan 25, 2012
  2. Matthieu MoyJan 25, 2012
  3. Felipe ContrerasJan 25, 2012
  4. Matthieu MoyJan 25, 2012
  5. Felipe ContrerasJan 28, 2012
  6. Junio C HamanoJan 26, 2012
  7. Felipe ContrerasJan 27, 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.