"git grep --no-index" doesn't do what it says on the tin?

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

"git grep --no-index" doesn't do what it says on the tin?

From: Nazri Ramliy <hidden>
Date: 2016-06-15 22:57:15

Hi,
From "git help grep":
      --no-index
           Search files in the current directory that is not managed by Git.

       --untracked
           In addition to searching in the tracked files in the working tree,
           search also in untracked files.
From the description above I would think that "git grep --no-index"
and "git grep --untracked" would behave differently, but it seems like
their behavior is the same:

        $ cd ~/src/git
        $ echo superman >> git.c
        $ echo superman >> foo.txt
        $ git grep --no-index superman
        foo.txt:1:superman
        git.c:588:superman
        $ git grep --untracked superman
        foo.txt:1:superman
        git.c:588:superman

I would expect the following behavior for "git grep --no-index":

        $ git grep --no-index superman
        foo.txt:1:superman
        $

That is, it won't search inside files that are managed by git.

nazri

Re: "git grep --no-index" doesn't do what it says on the tin?

From: Antoine Pelisse <hidden>
Date: 2016-06-15 22:57:15

On Wed, May 15, 2013 at 7:32 AM, Nazri Ramliy [off-list ref] wrote:
Hi,

From "git help grep":

      --no-index
           Search files in the current directory that is not managed by Git.

       --untracked
           In addition to searching in the tracked files in the working tree,
           search also in untracked files.
The difference is in the "not managed by Git". Inside a repository,
they will do the same thing. But only the first can work outside a
repository.

Cheers,
Antoine
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help