The "status" command recently learned to describe the
in-progress operation in its long output format (e.g.,
rebasing, am, etc). The color for this message defaults to
"normal" (i.e., no color). However, if the user has set
their default header color to something besides normal, then
the message st
On Sat, Jul 14, 2012 at 08:28:28AM -0400, Jeff King wrote:
> My intent was that this would also let "color.status.inprogress"
> override it, in case a user really wanted a green message or something.
> However, I notice that the original series did not add such a config
> option, so this color can
Jeff King writes:
> But given that this is not even configurable in the current code, I
> really wonder if it needs to have its own color at all. Do people really
> want to set the color of this message separately? Maybe we should just
> use WT_STATUS_HEADER instead.
I would prefer that myself,
Jeff King writes:
> Subject: [PATCH] status: color in-progress message like other header messages
My feeling is that these "in progress" messages would deserve to be more
visible than the usual headers (like "Not currently on any branch.",
which is both legit and likely to be a user-error). For
On Mon, Jul 16, 2012 at 11:59:45AM +0200, Matthieu Moy wrote:
> Jeff King writes:
>
> > Subject: [PATCH] status: color in-progress message like other header
> > messages
>
> My feeling is that these "in progress" messages would deserve to be more
> visible than the usual headers (like "Not cur
5 matches
Mail list logo
