git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: Lucien Kong <Lucien.Kong@ensimag.imag.fr>,
	Valentin Duperray <Valentin.Duperray@ensimag.imag.fr>,
	Franck Jonas <Franck.Jonas@ensimag.imag.fr>,
	Thomas Nguy <Thomas.Nguy@ensimag.imag.fr>,
	Huynh Khoi Nguyen Nguyen 
	<Huynh-Khoi-Nguyen.Nguyen@ensimag.imag.fr>,
	Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Subject: [PATCH] status: default in-progress color to header color
Date: Sat, 14 Jul 2012 08:28:29 -0400	[thread overview]
Message-ID: <20120714122828.GA6259@sigill.intra.peff.net> (raw)

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 sticks out. A much saner default is to pick the
user's header color, making this message match the rest of
the header.

We already do the same trick with the "onbranch" message.
Rather than expand the current conditional to list all types
of messages which will default back to the header color, we
can just default all "nil" colors to do so, simplifying the
code. That encompasses all of the current nil color slots,
and will likely cover any future ones that will be added.

Signed-off-by: Jeff King <peff@peff.net>
---
This goes on top of lk/more-helpful-status-hints.

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 cannot be configured at all. Furthermore, I think
the color formatting for this message is somewhat buggy.  Even if we set
it to green, you would end up with (imagine our header color is blue):

  <blue># On branch master<reset>
  <green># You are in the middle of a rebase.<reset>

when what you would probably want is:

  <blue># On branch master<reset>
  <blue># <reset><green>You are in the middle of a rebase.<reset>

I.e., the "#" bit should always be in the header color, and only the
message text should change colors. This is how the "onbranch" message is
handled.

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.

 wt-status.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/wt-status.c b/wt-status.c
index c749267..2f724b4 100644
--- a/wt-status.c
+++ b/wt-status.c
@@ -24,7 +24,7 @@ static char default_wt_status_colors[][COLOR_MAXLEN] = {
 	GIT_COLOR_GREEN,  /* WT_STATUS_LOCAL_BRANCH */
 	GIT_COLOR_RED,    /* WT_STATUS_REMOTE_BRANCH */
 	GIT_COLOR_NIL,    /* WT_STATUS_ONBRANCH */
-	GIT_COLOR_NORMAL, /* WT_STATUS_IN_PROGRESS */
+	GIT_COLOR_NIL,    /* WT_STATUS_IN_PROGRESS */
 };
 
 static const char *color(int slot, struct wt_status *s)
@@ -32,7 +32,7 @@ static const char *color(int slot, struct wt_status *s)
 	const char *c = "";
 	if (want_color(s->use_color))
 		c = s->color_palette[slot];
-	if (slot == WT_STATUS_ONBRANCH && color_is_nil(c))
+	if (color_is_nil(c))
 		c = s->color_palette[WT_STATUS_HEADER];
 	return c;
 }
-- 
1.7.10.5.40.gbbc17de

             reply	other threads:[~2012-07-14 12:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-14 12:28 Jeff King [this message]
2012-07-14 12:36 ` [PATCH] status: default in-progress color to header color Jeff King
2012-07-16  9:59   ` Matthieu Moy
2012-07-16 11:39     ` Jeff King
2012-07-14 20:20 ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120714122828.GA6259@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=Franck.Jonas@ensimag.imag.fr \
    --cc=Huynh-Khoi-Nguyen.Nguyen@ensimag.imag.fr \
    --cc=Lucien.Kong@ensimag.imag.fr \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=Thomas.Nguy@ensimag.imag.fr \
    --cc=Valentin.Duperray@ensimag.imag.fr \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).