Re: [PATCH] grep: provide a noop --recursive option
- Date: Fri, 5 Oct 2018 12:17:42 -0700
- From: Stefan Beller <sbeller@xxxxxxxxxx>
- Subject: Re: [PATCH] grep: provide a noop --recursive option
On Fri, Oct 5, 2018 at 6:05 AM Mischa POSLAWSKY <git@xxxxxxxx> wrote:
> Junio C Hamano wrote 2018-10-05 1:19 (-0700):
> > Stefan Beller <sbeller@xxxxxxxxxx> writes:
> > > git-grep is always file/tree recursive, but there is --recurse-submodules
> > > which is off by default. Instead of providing a short alias to a noop,
> > > we could use -r for submodules. (And if you happen to have no
> > > submodules, this is a noop for you)
> > I am not sure if it is an overall win for those who do have and use
> > submodules to easily be able to go recursive with a short-and-sweet
> > 'r', or even they want to work inside one project at a time most of
> > the time. If the latter, then using 'r' for recurse-submodules is
> > going to be a mistake (besides, other commands that have 'recursive'
> > typically use 'r' for its shorthand,and 'r' does not stand for
> > 'recurse-submodules' for them).
> Personally I would welcome a shorthand for --recurse-submodules,
> especially if --r^I no longer completes to this.
The new switch differs by one dash, so I'd think the double dashed
version would still autocomplete.
Unrelated to this, but more to submodules:
There is submodule.recurse which you may want to set.
Would you be interested in a more specific config option there?
(i.e. grep.recurseSubmodules to only apply to grep recursing into
submodules, just like fetch.recurseSubmodules only applies to fetch)
> It is also closer to the behaviour provided by grep -r as that recurses
> into submodules as well.
That sort of makes for the grep case, but not for other commands.
See the related discussion at