git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Neal Kreitzinger" <neal@rsss.com>
To: git@vger.kernel.org
Subject: color (red) for error messages on all git commands
Date: Wed, 24 Mar 2010 17:44:09 -0500	[thread overview]
Message-ID: <hoe4j3$2vg$1@dough.gmane.org> (raw)

Problem Scenario:  programmer doesn't pay attention to messages as he 
becomes more familiar with git and as a result doesn't notice error messages 
until its too late.  Mistakes take longer to remediate because the original 
error message was not resolved at the time it occurred.

Desired Solution:  configure git to display all error messages in color, 
e.g. red, so that the programmer does not overlook error messages.

Does anyone know how to configure this in git?


v/r,
Neal 

             reply	other threads:[~2010-03-24 22:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-24 22:44 Neal Kreitzinger [this message]
2010-03-24 22:58 ` color (red) for error messages on all git commands Sverre Rabbelier
2010-03-24 23:12   ` Alex Riesen
2010-03-25  8:43     ` Michael J Gruber
2010-03-25  8:46       ` [PATCH RFC/RFD] clone: quell the progress report from init Michael J Gruber
2010-03-25  9:02         ` Alex Riesen
2010-03-25  9:26           ` Michael J Gruber
2010-03-25 16:31         ` Tilo Schwarz
2010-03-26 19:32         ` Junio C Hamano
2010-03-26 20:16           ` Nicolas Pitre
2010-03-26 20:24             ` Junio C Hamano
2010-03-30  5:18             ` Junio C Hamano
2010-03-30  8:05               ` Michael J Gruber
2010-03-30  8:43               ` Alex Riesen
2010-04-01 22:03               ` [PATCH] clone: quell the progress report from init and report on clone Michael J Gruber
2010-04-02  7:28                 ` Junio C Hamano
2010-04-04 13:02                   ` Michael J Gruber
2010-04-23 12:37                     ` Michael J Gruber

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='hoe4j3$2vg$1@dough.gmane.org' \
    --to=neal@rsss.com \
    --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).