git/list[1] front-page[2] threads[3] people[4] search[5] about
 

color (red) for error messages on all git commands

From
NKNeal Kreitzinger <neal@rsss.com>
Date
Mar 24, 2010, 22:44 UTC
Message-ID
<hoe4j3$2vg$1@dough.gmane.org>

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

Next: Sverre Rabbelier
Message 1 of 18 in “color (red) for error messages on all git commands”
  1. Neal KreitzingerMar 24, 2010
  2. Sverre RabbelierMar 24, 2010
  3. Alex RiesenMar 24, 2010
  4. Michael J GruberMar 25, 2010
  5. clone: quell the progress report from initMichael J Gruber, Mar 25, 2010
  6. Alex RiesenMar 25, 2010
  7. Michael J GruberMar 25, 2010
  8. Tilo SchwarzMar 25, 2010
  9. Junio C HamanoMar 26, 2010
  10. Nicolas PitreMar 26, 2010
  11. Junio C HamanoMar 26, 2010
  12. Junio C HamanoMar 30, 2010
  13. Michael J GruberMar 30, 2010
  14. Alex RiesenMar 30, 2010
  15. clone: quell the progress report from init and report on cloneMichael J Gruber, Apr 1, 2010
  16. Junio C HamanoApr 2, 2010
  17. Michael J GruberApr 4, 2010
  18. clone: quell the progress report from init and report on cloneMichael J Gruber, Apr 23, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.