Rubén Justo <rjusto@xxxxxxxxx> writes:
> Hopefully, we'll find a way to avoid sending ANSI codes, on demand,
> without disabling it entirely with color.ui=never or any other global
> option. To make this usable:
>
> (1/2) Stage this hunk [y,n,q,a,d,j,J,g,/,s,e,p,|,?]? | vim -
>
> However, the current functionality meets my current needs, so I'm happy
> with it.
Yup, if it really is needed we could do || or anything "unusual" to
signal the unusual nature of the command.
Or ">" command can send the output to specified file without
coloring, and the user can do whatever they want to it.
In any case, unlike "Let's not just do pager, but have a facility to
pipe to anything and make the pager a default destination" that was
a natural match to the originally proposed behaviour, these two are
quite different and can be left totally outside the scope of the
topic.
> One final note; I preferred to model the help text this way:
>
> y - stage this hunk
> n - do not stage this hunk
> ...
> g - select a hunk to go to
> / - search for a hunk matching the given regex
> ...
> | - pipe the current hunk to the pager, or |<program> to use a program'
> ? - print help
That's fine.
The 'g' and '/' commands take _mandatory_ arguments, but we do not
even mention it in the help text. But we need to say something for
this new thing, because it is _optional_ and if you do not give a
program, it does not ask.
A possibility is to phrase it like so:
| - pipe the current hunk to the program (or "%s" by default)
and fill %s with the program you'd use if not given, i.e. initially
the value of the GIT_PAGER but updated to the last used program
after the user uses "|<program>" form to specify one.
