From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/1] Colorize some errors on stderr
Date: Fri, 16 Feb 2018 13:25:44 +0100 (STD) [thread overview]
Message-ID: <cover.1518783709.git.johannes.schindelin@gmx.de> (raw)
This is an RFC because it tries to introduce a fundamental new color feature:
Coloring messages *on stderr*.
So far, pretty much everything in color.[ch] assumed that you want to color
only stuff on stdout.
However, in this case, a user (who became a contributor!) wanted some messages
that are printed to stderr and were missed by his colleagues to be colored.
The contribution comes via Pull Request from the Git for Windows project:
https://github.com/git-for-windows/git/pull/1429
Now, what would be possible solutions for this?
- introduce `int fd` in `want_color()` (and callees) so that we can make
a distinction whether we want to detect whether stdout or stderr is connected
to a tty
- introduce a separate `want_color_stderr()` (we still would need to decide
whether we want a config setting for this)
- not color stderr, ever
Also, I did not have too much time to dig into the question how to test this in
Git's test suite. Do we already have tests that generate fake server-side errors
onto which I could piggy-back a new test case?
Thoughts? Suggestions? Help?
Ryan Dammrose (1):
Colorize push errors
advice.c | 42 +++++++++++++++++++++++++++++++++++++++--
builtin/push.c | 38 +++++++++++++++++++++++++++++++++++++
transport.c | 59 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
3 files changed, 136 insertions(+), 3 deletions(-)
base-commit: b2e45c695d09f6a31ce09347ae0a5d2cdfe9dd4e
Published-As: https://github.com/dscho/git/releases/tag/colorize-push-errors-v1
Fetch-It-Via: git fetch https://github.com/dscho/git colorize-push-errors-v1
--
2.16.1.windows.4
next reply other threads:[~2018-02-16 12:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 12:25 Johannes Schindelin [this message]
2018-02-16 12:25 ` [PATCH 1/1] Colorize push errors Johannes Schindelin
2018-02-16 19:21 ` [PATCH 0/1] Colorize some errors on stderr Junio C Hamano
2018-04-06 11:21 ` Johannes Schindelin
2018-04-05 22:48 ` [PATCH v2 0/4] Colorize push errors Johannes Schindelin
2018-04-05 22:48 ` [PATCH v2 1/4] color: introduce support for colorizing stderr Johannes Schindelin
2018-04-05 22:48 ` [PATCH v2 2/4] push: colorize errors Johannes Schindelin
2018-04-05 23:37 ` Jacob Keller
2018-04-06 11:15 ` Johannes Schindelin
2018-04-05 22:48 ` [PATCH v2 3/4] Add a test to verify that push errors are colorful Johannes Schindelin
2018-04-06 10:50 ` Eric Sunshine
2018-04-06 12:13 ` Johannes Schindelin
2018-04-05 22:48 ` [PATCH v2 4/4] Document the new color.* settings to colorize push errors/hints Johannes Schindelin
2018-04-06 10:56 ` Eric Sunshine
2018-04-06 12:15 ` Johannes Schindelin
2018-04-07 6:55 ` Eric Sunshine
2018-04-21 10:09 ` [PATCH v3 0/4] Colorize push errors Johannes Schindelin
2018-04-21 10:09 ` [PATCH v3 1/4] color: introduce support for colorizing stderr Johannes Schindelin
2018-04-21 10:10 ` [PATCH v3 2/4] push: colorize errors Johannes Schindelin
2018-04-21 10:10 ` [PATCH v3 3/4] Add a test to verify that push errors are colorful Johannes Schindelin
2018-04-21 10:10 ` [PATCH v3 4/4] Document the new color.* settings to colorize push errors/hints Johannes Schindelin
2018-04-06 18:48 ` [PATCH 0/1] Colorize some errors on stderr Ævar Arnfjörð Bjarmason
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=cover.1518783709.git.johannes.schindelin@gmx.de \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).