Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: vcs_info: '%' in payloads not escaped

Frank Terbeck wrote on Fri, Jan 06, 2017 at 11:41:59 +0100:
> Daniel Shahaf wrote:
> > Frank Terbeck wrote on Thu, Jan 05, 2017 at 17:27:06 +0100:
> [...]
> >> 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.
> >
> > A lot of special cases, how?  $git_applied_s contains a string derived
> > from git, so we know that any and all percent signs in it need escaping.
> The percent characters need escaping if the result is to be used in zsh
> prompts. In other cases, like tmux window titles, they don't. But maybe
> the hash sign (#) does, over there.
> I think this is already non-trivial in zsh itself, because there may be
> uses that exceed prompts. But in the general case, I don't think its
> possible.

Well, of course I'm not going to write an escape function that produces
a string that can be inserted, verbatim, into any context.  That's
mathematically impossible.

However, I do think this problem is solvable.  The string we produce in
$vcs_info_msg_N_ should have a defined escaping.  I would suggest to
define that that string is prompt-escaped — which would be consistent
with existing code, such as
    precmd() { print -Plr -- ${vcs_info_msg_0_} ${vcs_info_msg_1_} }
    setopt promptsubst
    PS1='${vcs_info_msg_0_}%# '
— and then, if people want to use that string in tmux, they can:
     1	local tmux_command
     2	print -v tmux_command -Pr -- $vcs_info_msg_0_
     3	tmux set-option set-titles-string ${vcs_info_msg_0_//'#'/##}

All of these code excerpts work today, and I will commit no patch that
breaks either of them.  So I'm still not sure what your concern is.

Suppose, for example, the string that is to be printed is "Lorem ipsum
50% Foo#Bar".  In this case, after `vcs_info` returns, $vcs_info_msg_0_
is set to "Lorem ipsum 50%% Foo#Bar"; the `print -v -Pr` de-doubles the
percent; and line three escapes the hash sign.  Perfectly predictable,
well-defined, consistent, generalizable, and all those other good
adjectives...  isn't it?



Messages sorted by: Reverse Date, Date, Thread, Author