From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <ericsunshine@charter.net>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
Patrick Steinhardt <ps@pks.im>,
Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: [PATCH v2 0/3] make chainlint output more newcomer-friendly
Date: Tue, 10 Sep 2024 10:31:06 -0700 [thread overview]
Message-ID: <xmqqfrq7fmat.fsf@gitster.g> (raw)
In-Reply-To: <20240910041013.68948-1-ericsunshine@charter.net> (Eric Sunshine's message of "Tue, 10 Sep 2024 00:10:10 -0400")
Eric Sunshine <ericsunshine@charter.net> writes:
> * new patch [1/3] -- motivated by Junio's observation[2] about
> availability of structured problem information -- takes advantage of
> that information directly rather than post-processing "?!...?!"
> sequences in the output stream
;-).
> * old patch [2/2] (now [3/3]) which drops "?!" decorations when emitting
> colored output to a terminal partially justified the change by
> claiming that the new "ERR" (or "ERR:") prefix is a good "needle" for
> a terminal's search feature, thus the noisy "?!" is no longer needed;
> however, I realized that "ERR" (or "ERR:") is, in fact, an awful
> needle since the string "err" (or "err:") is quite likely to
> legitimately appear in source text, hence I changed the prefix to
> "LINT:" (with the colon since Patrick found lack of colon
> confusing[3])
Nice; I prefer LINT over ERR quite a lot.
> Unfortunately, the included range-diff is a mess and pretty much useless
That's expected and OK after a large update of any series, which
often deserves to be read from cover to cover anyway.
> - $checked =~ s/(\s) \?!/$1?!/mg;
> - $checked =~ s/\?! (\s)/?!$1/mg;
> - $checked =~ s/\?!([^?]+)\?!/$erropen$1$errclose/mg;
;-)
prev parent reply other threads:[~2024-09-10 17:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 9:16 [PATCH 0/2] make chainlint output more newcomer-friendly Eric Sunshine
2024-08-29 9:16 ` [PATCH 1/2] chainlint: make error messages self-explanatory Eric Sunshine
2024-08-29 10:03 ` Patrick Steinhardt
2024-08-29 17:07 ` Jeff King
2024-08-29 18:10 ` Eric Sunshine
2024-08-29 18:01 ` Eric Sunshine
2024-08-29 15:39 ` Junio C Hamano
2024-08-29 22:04 ` Eric Sunshine
2024-08-30 18:41 ` Junio C Hamano
2024-08-29 9:16 ` [PATCH 2/2] chainlint: reduce annotation noise-factor Eric Sunshine
2024-08-29 10:03 ` Patrick Steinhardt
2024-08-29 17:10 ` Jeff King
2024-08-29 18:37 ` Eric Sunshine
2024-08-29 18:28 ` Eric Sunshine
2024-08-29 15:55 ` Junio C Hamano
2024-08-30 23:30 ` Eric Sunshine
2024-08-30 23:51 ` Junio C Hamano
2024-09-10 4:10 ` [PATCH v2 0/3] make chainlint output more newcomer-friendly Eric Sunshine
2024-09-10 4:10 ` [PATCH v2 1/3] chainlint: don't be fooled by "?!...?!" in test body Eric Sunshine
2024-09-10 16:48 ` Junio C Hamano
2024-09-10 4:10 ` [PATCH v2 2/3] chainlint: make error messages self-explanatory Eric Sunshine
2024-09-10 7:48 ` Patrick Steinhardt
2024-09-10 4:10 ` [PATCH v2 3/3] chainlint: reduce annotation noise-factor Eric Sunshine
2024-09-10 7:48 ` Patrick Steinhardt
2024-09-10 8:14 ` Eric Sunshine
2024-09-10 15:42 ` Junio C Hamano
2024-09-10 22:17 ` Eric Sunshine
2024-09-10 6:44 ` [PATCH v2 0/3] make chainlint output more newcomer-friendly Jeff King
2024-09-10 17:31 ` Junio C Hamano [this message]
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=xmqqfrq7fmat.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ericsunshine@charter.net \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=ps@pks.im \
--cc=sunshine@sunshineco.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).