From: Stefan Beller <sbeller@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jacob Keller <jacob.keller@gmail.com>,
Jonathan Tan <jonathantanmy@google.com>,
Brandon Williams <bmwill@google.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Michael Haggerty <mhagger@alum.mit.edu>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Jun 2017, #03; Mon, 5)
Date: Wed, 14 Jun 2017 11:44:50 -0700 [thread overview]
Message-ID: <CAGZ79kasPxbGLUEkvQ0sOJtjTvGO0BvAeUF_LeOiFNEhd7VBfg@mail.gmail.com> (raw)
In-Reply-To: <xmqqo9tq51yq.fsf@gitster.mtv.corp.google.com>
On Wed, Jun 14, 2017 at 2:54 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Stefan Beller <sbeller@google.com> writes:
>
>> The color experts agreed that (3) might be the best solution
>> as this gives most flexibility:
>>
>> "I would be happy as I can configure the bounds highlighting
>> to not exist, it would degenerate to a pure Zebra, which is
>> very simple to understand. Junio seemed to like (2) a lot, so
>> he would configure both dim colors to be 'context', but configure
>> the highlight colors to be attention drawing. So everybody would
>> be happy. It is also not too many colors, we are good at for loops."
>
> Another thing I found a bit confusing in the description of choices
> in the documentation was that description for some began with "Based
> on X.", and as a plain reader, I couldn't tell if that is saying
> "the implementation happens to be similar or shares code with X"
> (which is not all that interesting to the end user) or "the meaning
> this mode tries to convey is the same as X but the presentation is a
> bit different" (in which case the end user is hinted that it is
> benefitial to understand what informacion the mode X shows and how).
it is the latter, as I wanted to save typing. Maybe it was savings
at the wrong place.
>
> For example, I view what I prefer (i.e. (2)) as a variant of Zebra
> (i.e. (1)).
Ok, so in a reroll I'll add Zebra as the base (It conveys all
information that we have, any further modifications is just giving
a better finish to the painting.) and then make commits on top of it
adding the taping and water-dunking method on top.
By organizing it in multiple commits the algorithm may become clearer.
> Conceptually, you paint the diff output using water
> soluble paint into a Zebra pattern, then apply thin strips of
> protective tape to places where two Zebra colors are adjacent to
> each other (i.e. do not cover the boundary between a block of a
> Zebra colored moved lines and a block of context lines), dunk the
> whole thing in water and then remove the strips of tape. Regions
> covered by the strips of tape will retain the Zebra colors, while
> the remainder of the Zebra colored part are colored in a much subdued
> way. Understanding how Zebra mode marks the moved lines would help
> understanding its output, but your implementation may not share much
> code with the actual implementation of Zebra-painting.
>
> Thanks.
>
Thanks,
Stefan
next prev parent reply other threads:[~2017-06-14 18:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 3:59 What's cooking in git.git (Jun 2017, #03; Mon, 5) Junio C Hamano
2017-06-05 18:23 ` Stefan Beller
2017-06-06 1:10 ` Junio C Hamano
2017-06-06 6:52 ` Jacob Keller
2017-06-08 5:41 ` Jacob Keller
2017-06-13 22:19 ` Stefan Beller
2017-06-14 9:54 ` Junio C Hamano
2017-06-14 18:44 ` Stefan Beller [this message]
2017-06-06 6:44 ` Jacob Keller
2017-06-06 9:50 ` Michael Haggerty
2017-06-06 22:05 ` Jacob Keller
2017-06-07 18:28 ` Stefan Beller
2017-06-07 21:58 ` Ævar Arnfjörð Bjarmason
2017-06-07 22:05 ` Stefan Beller
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=CAGZ79kasPxbGLUEkvQ0sOJtjTvGO0BvAeUF_LeOiFNEhd7VBfg@mail.gmail.com \
--to=sbeller@google.com \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jacob.keller@gmail.com \
--cc=jonathantanmy@google.com \
--cc=jrnieder@gmail.com \
--cc=mhagger@alum.mit.edu \
/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).