Not implemented Show `context` trailing (`A` -- after), or leading (`B` -- before), or both (`C` -- context) lines, and place a line containing `--` between contiguous groups of matches.

Not implemented When giving multiple pattern expressions combined with `--or`, this flag is specified to limit the match to files that have lines to match all of them.

Not implemented ( ... ):: Specify how multiple patterns are combined using Boolean expressions. `--or` is the default operator. `--and` has higher precedence than `--or`. `-e` has to be used for all patterns.

Not implemented Show `context` trailing (`A` -- after), or leading (`B` -- before), or both (`C` -- context) lines, and place a line containing `--` between contiguous groups of matches.

Not implemented Use POSIX extended/basic regexp for patterns. Default is to use basic regexp.

Not implemented Show `context` trailing (`A` -- after), or leading (`B` -- before), or both (`C` -- context) lines, and place a line containing `--` between contiguous groups of matches.

Not implemented Instead of searching in the working tree files, check the blobs registered in the index file.

Not implemented Show colored matches.

Not implemented Instead of showing every matched line, show the number of lines that match.

Not implemented The next parameter is the pattern. This option has to be used for patterns starting with - and should be used in scripts passing user input to grep. Multiple patterns are combined by 'or'.

Not implemented Use POSIX extended/basic regexp for patterns. Default is to use basic regexp.

Not implemented Read patterns from , one per line.

Not implemented Instead of showing every matched line, show only the names of files that contain (or do not contain) matches. For better compatibility with 'git-diff', --name-only is a synonym for --files-with-matches.

Not implemented Instead of showing every matched line, show only the names of files that contain (or do not contain) matches. For better compatibility with 'git-diff', --name-only is a synonym for --files-with-matches.

Not implemented Use fixed strings for patterns (don't interpret pattern as a regex).

Not implemented When run from a subdirectory, the command usually outputs paths relative to the current directory. This option forces paths to be output relative to the project top directory.

Not implemented By default, the command shows the filename for each match. `-h` option is used to suppress this output. `-H` is there for completeness and does not do anything except it overrides `-h` given earlier on the command line.

Not implemented Don't match the pattern in binary files.

Not implemented Ignore case differences between the patterns and the files.

Not implemented Select non-matching lines.

Not implemented For each pathspec given on command line, descend at most levels of directories. A negative value means no limit.

Not implemented Prefix the line number to matching lines.

Not implemented Instead of showing every matched line, show only the names of files that contain (or do not contain) matches. For better compatibility with 'git-diff', --name-only is a synonym for --files-with-matches.

Not implemented Turn off match highlighting, even when the configuration file gives the default to color output.

Not implemented ( ... ):: Specify how multiple patterns are combined using Boolean expressions. `--or` is the default operator. `--and` has higher precedence than `--or`. `-e` has to be used for all patterns.

Not implemented Output \0 instead of the character that normally follows a file name.

Not implemented ( ... ):: Specify how multiple patterns are combined using Boolean expressions. `--or` is the default operator. `--and` has higher precedence than `--or`. `-e` has to be used for all patterns.

Not implemented Show the preceding line that contains the function name of the match, unless the matching line is a function name itself. The name is determined in the same way as 'git diff' works out patch hunk headers (see 'Defining a custom hunk-header' in linkgit:gitattributes[5]).

Not implemented Process binary files as if they were text.

Not implemented Match the pattern only at word boundary (either begin at the beginning of a line, or preceded by a non-word character; end at the end of a line or followed by a non-word character).