From: "Dirk Süsserott" <newsletter@dirk.my1.cc>
To: Git Mailing List <git@vger.kernel.org>
Subject: Re: gitk: how to apply '--color-words' to the diff command
Date: Tue, 18 Mar 2008 21:58:40 +0100 [thread overview]
Message-ID: <47E02D00.2080703@dirk.my1.cc> (raw)
In-Reply-To: <47DEC41D.9050409@dirk.my1.cc>
>
> a few days ago I found a patch for gitk that adds a checkbox 'Ignore
> space change' to the gitk GUI and -- when clicked -- adds the '-w'
> switch to the diff command. I found that a very convenient way to see
> 'what has really changed'. The patch was contributed by Steffen
> Prohaska and has sha1 b9b86007e27d9a06d58feab618a5be1d491ed13e in the
> git://git.kernel.org/pub/scm/git/git.git repository.
>
> Inspired by this, I thought a '--color-words' switch would be even more
> convenient. I took the patch as a template and kinda replaced all
> occurences of '-w' with '--color-words' (do not take this literally).
>
> Unfortunately gitk then shows the diffs not colorized but with those
> ugly escape sequences instead. I'm not a Python person and just able
> to 'copy and waste', but probably some of you had the same idea and
> got it right.
>
I'm not only not a Python person but also not a Tcl person. Did't even
figure out the difference. Sorry for that.
However, what I figured out is that it's not as simple as I thought: The
colorization in question is hard coded in the last 'else' branch of
'getblobdiffline'. When a line starts with a '+' or '-', then it's shown
in green or red. To support the --color-words switch it would be
neccessary to actually parse diff's output wrt. to the colors.
Sorry for the noise.
Dirk
prev parent reply other threads:[~2008-03-20 1:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 19:18 gitk: how to apply '--color-words' to the diff command Dirk Süsserott
2008-03-18 20:55 ` Dirk Süsserott
2008-03-18 20:58 ` Dirk Süsserott [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=47E02D00.2080703@dirk.my1.cc \
--to=newsletter@dirk.my1.cc \
--cc=git@vger.kernel.org \
/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).