A common thing to grep for is the name of a symbol. This
patch teaches the completion for "git grep" to look in
a 'tags' file, if present, to complete a pattern. For
example, in git.git:
$ make tags
$ git grep get_sha1<Tab><Tab>
get_sha1 get_sha1_oneline
get_sha1_1 get_sha1_with_context
get_sha1_basic get_sha1_with_context_1
get_sha1_hex get_sha1_with_mode
get_sha1_hex_segment get_sha1_with_mode_1
get_sha1_mb
Signed-off-by: Jeff King <peff@xxxxxxxx>
---
It's debatable whether this belongs in the generic completion code, as
it really only works if your project uses ctags. But I find it to be a
huge timesaver for finding callsites of functions, especially when
coupled with "git jump grep" from the previous patch.
Undoubtedly you can do something similar with cscope, or with an editor
plugin, but using grep feels very natural and simple to me.
For using with "git jump grep", I do this:
# much easier to type
git config --global alias.vgrep 'jump grep'
# and set up completion for it, too
cat >>~/.bashrc
_git_vgrep() {
_git_grep
}
contrib/completion/git-completion.bash | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
index 8648a36..f4ab13d 100755
--- a/contrib/completion/git-completion.bash
+++ b/contrib/completion/git-completion.bash
@@ -1432,6 +1432,10 @@ _git_gitk ()
_gitk
}
+_git_grep_ctag_match() {
+ awk -v ORS=' ' "/^${1////\\/}/ { print \$1 }" "$2"
+}
+
_git_grep ()
{
__git_has_doubledash && return
@@ -1454,6 +1458,13 @@ _git_grep ()
;;
esac
+ case "$COMP_CWORD,$prev" in
+ 2,*|*,-*)
+ test -r tags || return
+ COMPREPLY=( $(compgen -W "`_git_grep_ctag_match "$cur" tags`") )
+ return
+ esac
+
__gitcomp "$(__git_refs)"
}
--
1.7.7.rc3.37.gc4dc8
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html