[PATCH 4/9] add missing long option to 'git grep' bash competion

[PATCH 4/9] add missing long option to 'git grep' bash competion

[Emmanuel Trillaud]

according to the 'git-grep' man page, the following long options are missing
from the 'git grep' bash completion :
--null
--color
--no-color

Signed-off-by: Emmanuel Trillaud <etrillaud@gmail.com>
---
 contrib/completion/git-completion.bash |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/contrib/completion/git-completion.bash
b/contrib/completion/git-completion.bash
index f56733b..a4e78d5 100755
--- a/contrib/completion/git-completion.bash
+++ b/contrib/completion/git-completion.bash
@@ -1057,7 +1057,9 @@ _git_grep ()
 			--extended-regexp --basic-regexp --fixed-strings
 			--files-with-matches --name-only
 			--files-without-match
+			--null
 			--count
+			--color --no-color
 			--and --or --not --all-match
 			"
 		return
-- 
1.6.4

Re: [PATCH 4/9] add missing long option to 'git grep' bash competion

[Junio C Hamano]

Emmanuel Trillaud <etrillaud@gmail.com> writes:

> according to the 'git-grep' man page, the following long options are missing
> from the 'git grep' bash completion :
> --null
> --color
> --no-color

I do not think completion's purpose should be to offer everything
available under the sun, so "according to manpage these are missing" can
never be a good justification for patches in this series.

Does it even make sense to complete --null in an interactive invocation?

Re: [PATCH 4/9] add missing long option to 'git grep' bash competion

[Emmanuel Trillaud]

> > according to the 'git-grep' man page, the following long options are
> > missing from the 'git grep' bash completion :
> > --null
> > --color
> > --no-color
> 
> I do not think completion's purpose should be to offer everything
> available under the sun, so "according to manpage these are missing" can
> never be a good justification for patches in this series.
When I saw that completion for the long options of 'git checkout' was
mising, I just start looking around the docs to see if there wasn't other
git commands with some missing completions. I see now it was a wrong way
to update the git bash completion. I will soon come back with a new set
of (more reasonnable) patches.

Emmanuel