From: Alex Riesen <raa.lkml@gmail.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Neal Kreitzinger <neal@rsss.com>, git@vger.kernel.org
Subject: Re: color (red) for error messages on all git commands
Date: Thu, 25 Mar 2010 00:12:28 +0100 [thread overview]
Message-ID: <81b0412b1003241612m41f6ae2ctaa5b89ed37b58da2@mail.gmail.com> (raw)
In-Reply-To: <fabb9a1e1003241558t4c4c5cf8t3a7d9b9856937c4f@mail.gmail.com>
On Wed, Mar 24, 2010 at 23:58, Sverre Rabbelier <srabbelier@gmail.com> wrote:
> On Wed, Mar 24, 2010 at 23:44, Neal Kreitzinger <neal@rsss.com> wrote:
>> Desired Solution: configure git to display all error messages in color,
>> e.g. red, so that the programmer does not overlook error messages.
It is considered a good behavior for a UNIX program only to display
something if there is an error. Git just tries to follow this tradition.
> That's actually something I run into as well, I am so used to git just
> doing what I want that I don't notice the error messages when they
> occur. If this is indeed desired (probably controlled by color.warning
> and color.error?) it should be fairly easy to implement (see usage.c).
That said, I also like the idea. Don't forget to check for tty in the patch.
next prev parent reply other threads:[~2010-03-24 23:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 22:44 color (red) for error messages on all git commands Neal Kreitzinger
2010-03-24 22:58 ` Sverre Rabbelier
2010-03-24 23:12 ` Alex Riesen [this message]
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=81b0412b1003241612m41f6ae2ctaa5b89ed37b58da2@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=neal@rsss.com \
--cc=srabbelier@gmail.com \
/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).