From: Jakub Narebski <jnareb@gmail.com>
To: Wincent Colaiuta <win@wincent.com>
Cc: "git@vger.kernel.org List" <git@vger.kernel.org>
Subject: Re: RFC: git diff colorization idea
Date: Fri, 23 Jan 2009 10:40:52 -0800 (PST) [thread overview]
Message-ID: <m3iqo5yiek.fsf@localhost.localdomain> (raw)
In-Reply-To: <53497057-1ADE-4300-9F35-B218959606FE@wincent.com>
Wincent Colaiuta <win@wincent.com> writes:
> Lately I've been wishing that Git's diff output were colorized in a
> way that combines the standard line-by-line colorizing with the word-
> by-word colorizing you get with --color-words.
I like this idea, also because Emacs ediff / ediff3 / emerge uses it,
from what I understand under the name of 'refinement'.
>
> Pictures speak louder than words, so here are some to show what I mean:
>
> http://www.flickr.com/photos/wincent-colaiuta/sets/72157612877491482/
>
[...]
There was some discussion in this thread on how to do this, whether
with --refine / --color-chars we shoud ony highlight differences, or
whether for example use reverse (i.e. background green or background
red), or other red / other green, or perhaps bold, or perhaps
underline to highlight regions in line which differ
> - Meld: http://meld.sourceforge.net/meld_file1.png
Not extremly good example, as it uses equivalent of context diff
format (-,+,!) with added, removed and _changed_ lines, and not
unified diff format (only added / removed lines).
> Would people be interested in seeing this feature go in? [...]
+1 from me
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2009-01-23 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 0:00 RFC: git diff colorization idea Wincent Colaiuta
2009-01-23 0:32 ` Junio C Hamano
2009-01-23 6:16 ` Wincent Colaiuta
2009-01-23 6:45 ` Junio C Hamano
2009-01-23 8:28 ` Nanako Shiraishi
2009-01-23 18:40 ` Jakub Narebski [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=m3iqo5yiek.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=win@wincent.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).