From: Michael J Gruber <git@drmicha.warpmail.net>
To: Git Mailing List <git@vger.kernel.org>
Subject: --color-diff='.' considered useful
Date: Mon, 16 Nov 2015 15:25:55 +0100 [thread overview]
Message-ID: <5649E773.7040705@drmicha.warpmail.net> (raw)
git tip of the day:
git diff --color-words='.'
git show --color-words='.'
That will help you find that 1 character change that a failed default
word split hides from your eyes.
I guess everyone here will know already, but I found that super useful
and much easier than trying to get a meaningful word split for that 100+
char TeX source line without a single space...
Cheers,
Michael
next reply other threads:[~2015-11-16 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 14:25 Michael J Gruber [this message]
2015-11-16 14:34 ` --color-diff='.' considered useful Matthieu Moy
2015-11-20 13:36 ` [PATCH] Documentation/diff: give --word-diff-regex=. example Michael J Gruber
2015-11-20 14:59 ` Matthieu Moy
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=5649E773.7040705@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--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).