From: Jeff King <peff@peff.net>
To: George King <george.w.king@gmail.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Stefan Beller" <sbeller@google.com>, git <git@vger.kernel.org>
Subject: Re: Difficulty with parsing colorized diff output
Date: Wed, 12 Dec 2018 07:49:09 -0500 [thread overview]
Message-ID: <20181212124908.GA5380@sigill.intra.peff.net> (raw)
In-Reply-To: <EB1AF739-F97B-4905-9736-2A003722AD9A@gmail.com>
On Tue, Dec 11, 2018 at 11:41:18AM -0500, George King wrote:
> I first started playing around with terminal colors about 5 years ago,
> and I recall learning the hard way that Apple Terminal at least
> behaves very strangely when you have background colors cross line
> boundaries: background colors disappeared when I scrolled lines back
> into view. I filed a bug thinking it couldn't be right and Apple
> closed it as behaving according to compatibility expectations. I never
> figured out whether they had misunderstood my report or if old
> terminals were just that crazy. Instead I decided that the safe thing
> to do was reset after every line. Perhaps some git author reached the
> same conclusion.
Yes, that's exactly it. Certain codes do not do well as they cross
lines. It's been long enough that I don't remember the details, and a
quick grep of the archive found too many results for me to bother wading
through.
-Peff
prev parent reply other threads:[~2018-12-12 12:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-08 0:09 Difficulty with parsing colorized diff output George King
2018-12-08 7:16 ` Jeff King
2018-12-11 3:26 ` Stefan Beller
2018-12-11 10:17 ` Jeff King
2018-12-11 14:47 ` George King
2018-12-11 16:28 ` Ævar Arnfjörð Bjarmason
2018-12-11 16:41 ` George King
2018-12-11 18:55 ` George King
2018-12-12 13:52 ` Jeff King
2018-12-12 12:49 ` Jeff King [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
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=20181212124908.GA5380@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=avarab@gmail.com \
--cc=george.w.king@gmail.com \
--cc=git@vger.kernel.org \
--cc=sbeller@google.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).