git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Lénaïc Huard" <lenaic@lhuard.fr>
Cc: git@vger.kernel.org, "Martin Ågren" <martin.agren@gmail.com>
Subject: Re: [PATCH 0/1] grep: align default colors with GNU grep ones
Date: Thu, 16 Dec 2021 13:59:39 -0800	[thread overview]
Message-ID: <xmqqh7b88b3o.fsf@gitster.g> (raw)
In-Reply-To: <20211216115622.85506-1-lenaic@lhuard.fr> ("Lénaïc Huard"'s message of "Thu, 16 Dec 2021 12:56:21 +0100")

Lénaïc Huard <lenaic@lhuard.fr> writes:

> git-grep shares a lot of options with the standard grep tool.
> Like GNU grep, it has coloring options to highlight the matching text.
> And like it, it has options to customize the various colored parts.
>
> This patch updates the default git-grep colors to make them match the
> GNU grep default ones [1].
>
> It was possible to get the same result by setting the various `color.grep.<slot>`
> options, but this patch makes `git grep --color` share the same color scheme as
> `grep --color` by default without any user configuration.

I am not a huge fan of adjusting our defaults to other people's
default, since it will lead do an inevitable "Why don't they adjust
to match ours?" question, plus "We've been happily using the default
coloring, and you suddenly changed it to something ugly. We want our
color back and we do not care that now you match what GNU does".

The UI color choice is so personal, which does not help us either.

Having said that, I'll keep an eye on what others say on this
thread.

Thanks.


  parent reply	other threads:[~2021-12-16 21:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16 11:56 [PATCH 0/1] grep: align default colors with GNU grep ones Lénaïc Huard
2021-12-16 11:56 ` [PATCH 1/1] " Lénaïc Huard
2021-12-16 21:59 ` Junio C Hamano [this message]
2022-01-03 22:40   ` [PATCH 0/1] " Junio C Hamano
2022-01-05  8:21     ` Lénaïc Huard
2022-01-05  8:18 ` [PATCH v2 " Lénaïc Huard
2022-01-05  8:18   ` [PATCH v2 1/1] " Lénaïc Huard

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=xmqqh7b88b3o.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=lenaic@lhuard.fr \
    --cc=martin.agren@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).