Re: [PATCH] _git: Fix __git_recent_branches for case when commit has empty message

[WGH <wgh@torlan.ru>]

On 2/1/20 3:09 AM, Daniel Shahaf wrote:
> Not on my machine.
>
> First, the unidiff was improperly serialized: the spaces at the start
> of each context line were converted to non-breaking spaces (U+00A0).

Oh, damn, despite all my efforts, Thunderbird still messed the patch up. Sigh. (gotta finally find some sane mail client)

Anyway, copypasting it from the mailing list archive results in something that applies cleanly: https://www.zsh.org/mla/workers/2020/msg00190.html

> I applied the patch manually, and completion did work, but stderr was
> spammed with two warnings:
>
> +__git_recent_branches:21>   local $'z=\C-@'
> __git_recent_branches:21: command not found:

That isn't supposed to happen. This should merely assign a string contained a single null byte to variable z. Maybe you didn't clean up all those NBSP?

>  
> +__git_recent_branches:22> _call_program all-descriptions 'git --no-pager for-each-ref --format='\''%(refname)%00%(subject)'\' refs/heads/master --                                                                
> __git_recent_branches:22: unknown file attribute:

Likewise, I have no clue what it is.