Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: vcs_info: '%' in payloads not escaped
- X-seq: zsh-workers 40275
- From: Frank Terbeck <ft@xxxxxxxxxxxxxxxxxxx>
- To: Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>
- Subject: Re: vcs_info: '%' in payloads not escaped
- Date: Thu, 05 Jan 2017 17:27:06 +0100
- Cc: zsh-workers@xxxxxxx
- In-reply-to: <20170105160730.GA21106@fujitsu.shahaf.local2> (Daniel Shahaf's message of "Thu, 5 Jan 2017 16:07:30 +0000")
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <20161227150507.GA20351@fujitsu.shahaf.local2> <20170105160730.GA21106@fujitsu.shahaf.local2>
Hey Daniel!
Daniel Shahaf wrote:
[...]
> How about the following?
> else
> git_applied_s=""
> fi
> + git_applied_s=${git_applied_s//'%'/%%}
> else
[...]
> git_patches_unapplied=${#git_patches_unapplied}
> + git_patches_unapplied=${git_patches_unapplied//'%'/%%}
> else
I honestly don't know. Isn't this like kind-of-predictable behavior
versus a — potentially — a lot of special cases? I don't think that it's
possible to get this right in the general case. It's in-band data that
is indistinguishable from data that is interpreted by something that
interprets zsh's prompt language.
Regards, Frank
--
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
-- RFC 1925
Messages sorted by:
Reverse Date,
Date,
Thread,
Author