diff options
author | Taylor Blau <me@ttaylorr.com> | 2018-07-09 15:33:47 -0500 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2018-07-09 14:15:28 -0700 |
commit | 9d8db06eb4a5d5577db559a0059a377914c1ce5a (patch) | |
tree | a0ef841c1f6cd361d25b5c9f0e25337eb4a1c38d /diffcore-pickaxe.c | |
parent | grep.c: extract show_line_header() (diff) | |
download | tgif-9d8db06eb4a5d5577db559a0059a377914c1ce5a.tar.xz |
grep.c: teach 'git grep --only-matching'
Teach 'git grep --only-matching', a new option to only print the
matching part(s) of a line.
For instance, a line containing the following (taken from README.md:27):
(`man gitcvs-migration` or `git help cvs-migration` if git is
Is printed as follows:
$ git grep --line-number --column --only-matching -e git -- \
README.md | grep ":27"
README.md:27:7:git
README.md:27:16:git
README.md:27:38:git
The patch works mostly as one would expect, with the exception of a few
considerations that are worth mentioning here.
Like GNU grep, this patch ignores --only-matching when --invert (-v) is
given. There is a sensible answer here, but parity with the behavior of
other tools is preferred.
Because a line might contain more than one match, there are special
considerations pertaining to when to print line headers, newlines, and
how to increment the match column offset. The line header and newlines
are handled as a special case within the main loop to avoid polluting
the surrounding code with conditionals that have large blocks.
Signed-off-by: Taylor Blau <me@ttaylorr.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'diffcore-pickaxe.c')
0 files changed, 0 insertions, 0 deletions