summaryrefslogtreecommitdiffstats
path: root/contrib/git-jump/README
diff options
context:
space:
mode:
authorJeff King <peff@peff.net>2016-07-22 18:35:19 +0200
committerJunio C Hamano <gitster@pobox.com>2016-07-22 21:33:58 +0200
commit1af9c6096a7ec6cba3a5f7d359cb1caf2152496a (patch)
treebc56594f191ac3857c1e416866c85465f0173694 /contrib/git-jump/README
parentcontrib/git-jump: fix greedy regex when matching hunks (diff)
downloadgit-1af9c6096a7ec6cba3a5f7d359cb1caf2152496a.tar.xz
git-1af9c6096a7ec6cba3a5f7d359cb1caf2152496a.zip
contrib/git-jump: add whitespace-checking mode
If you have whitespace errors in lines you've introduced, it can be convenient to be able to jump directly to them for fixing. You can't quite use "git jump diff" for this, because though it passes arbitrary options to "git diff", it expects to see an actual unified diff in the output. Whereas "git diff --check" actually produces lines that look like compiler quickfix lines already, meaning we just need to run it and feed the output directly to the editor. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'contrib/git-jump/README')
-rw-r--r--contrib/git-jump/README4
1 files changed, 3 insertions, 1 deletions
diff --git a/contrib/git-jump/README b/contrib/git-jump/README
index 1cebc328cb..3e0b65b9b3 100644
--- a/contrib/git-jump/README
+++ b/contrib/git-jump/README
@@ -29,7 +29,7 @@ Obviously this trivial case isn't that interesting; you could just open
`foo.c` yourself. But when you have many changes scattered across a
project, you can use the editor's support to "jump" from point to point.
-Git-jump can generate three types of interesting lists:
+Git-jump can generate four types of interesting lists:
1. The beginning of any diff hunks.
@@ -37,6 +37,8 @@ Git-jump can generate three types of interesting lists:
3. Any grep matches.
+ 4. Any whitespace errors detected by `git diff --check`.
+
Using git-jump
--------------