Linux "grep" Command Line Options and Examples
print lines matching a pattern

grep searches for PATTERN in each FILE. A FILE of “-” stands for standard input. If no FILE is given, recursive searches examine the working directory, and nonrecursive searches read standard input.


Usage:

grep [OPTIONS] PATTERN [FILE...]
    grep [OPTIONS] -e PATTERN ... [FILE...]
    grep [OPTIONS] -f FILE ... [FILE...]






Command Line Options:

--help
Output a usage message and exit.
grep --help ...
-V
Output the version number of grep and exit.Matcher Selection
grep -V ...
-E
Interpret PATTERN as an extended regular expression (ERE, see below).
grep -E ...
-F
Interpret PATTERN as a list of fixed strings (instead of regular expressions), separated by newlines, any of which is to bematched.
grep -F ...
-G
Interpret PATTERN as a basic regular expression (BRE, see below). This is the default.
grep -G ...
-P
Interpret the pattern as a Perl-compatible regular expression (PCRE). This is experimental and grep -P may warn ofunimplemented features.Matching Control
grep -P ...
-e
Use PATTERN as the pattern. If this option is used multiple times or is combined with the -f (--file) option, search for allpatterns given. This option can be used to protect a pattern beginning with “-”.
grep -e ...
-f
Obtain patterns from FILE, one per line. If this option is used multiple times or is combined with the -e (--regexp) option,search for all patterns given. The empty file contains zero patterns, and therefore matches nothing.
grep -f ...
-i
Ignore case distinctions, so that characters that differ only in case match each other.
grep -i ...
-v
Invert the sense of matching, to select non-matching lines.
grep -v ...
-w
Select only those lines containing matches that form whole words. The test is that the matching substring must either be atthe beginning of the line, or preceded by a non-word constituent character. Similarly, it must be either at the end of theline or followed by a non-word constituent character. Word-constituent characters are letters, digits, and the underscore.This option has no effect if -x is also specified.
grep -w ...
-x
Select only those matches that exactly match the whole line. For a regular expression pattern, this is like parenthesizingthe pattern and then surrounding it with ^ and $.
grep -x ...
-y
General Output Control
grep -y ...
-c
Suppress normal output; instead print a count of matching lines for each input file. With the -v, --invert-match option (seebelow), count non-matching lines.
grep -c ...
--color[
Surround the matched (non-empty) strings, matching lines, context lines, file names, line numbers, byte offsets, andseparators (for fields and groups of context lines) with escape sequences to display them in color on the terminal. Thecolors are defined by the environment variable GREP_COLORS. The deprecated environment variable GREP_COLOR is stillsupported, but its setting does not have priority. WHEN is never, always, or auto.
grep --color[ ...
-L
Suppress normal output; instead print the name of each input file from which no output would normally have been printed. Thescanning will stop on the first match.
grep -L ...
-l
Suppress normal output; instead print the name of each input file from which output would normally have been printed. Thescanning will stop on the first match.
grep -l ...
-m
Stop reading a file after NUM matching lines. If the input is standard input from a regular file, and NUM matching lines areoutput, grep ensures that the standard input is positioned to just after the last matching line before exiting, regardless ofthe presence of trailing context lines. This enables a calling process to resume a search. When grep stops after NUMmatching lines, it outputs any trailing context lines. When the -c or --count option is also used, grep does not output acount greater than NUM. When the -v or --invert-match option is also used, grep stops after outputting NUM non-matchinglines.
grep -m ...
-o
Print only the matched (non-empty) parts of a matching line, with each such part on a separate output line.
grep -o ...
-q
Quiet; do not write anything to standard output. Exit immediately with zero status if any match is found, even if an errorwas detected. Also see the -s or --no-messages option.
grep -q ...
-s
Suppress error messages about nonexistent or unreadable files.Output Line Prefix Control
grep -s ...
-b
Print the 0-based byte offset within the input file before each line of output. If -o (--only-matching) is specified, printthe offset of the matching part itself.
grep -b ...
-H
Print the file name for each match. This is the default when there is more than one file to search.
grep -H ...
-h
Suppress the prefixing of file names on output. This is the default when there is only one file (or only standard input) tosearch.
grep -h ...
--label
Display input actually coming from standard input as input coming from file LABEL. This is especially useful whenimplementing tools like zgrep, e.g., gzip -cd foo.gz | grep --label=foo -H something. See also the -H option.
grep --label ...
-n
Prefix each line of output with the 1-based line number within its input file.
grep -n ...
-T
Make sure that the first character of actual line content lies on a tab stop, so that the alignment of tabs looks normal.This is useful with options that prefix their output to the actual content: -H,-n, and -b. In order to improve theprobability that lines from a single file will all start at the same column, this also causes the line number and byte offset(if present) to be printed in a minimum size field width.
grep -T ...
-u
Report Unix-style byte offsets. This switch causes grep to report byte offsets as if the file were a Unix-style text file,i.e., with CR characters stripped off. This will produce results identical to running grep on a Unix machine. This optionhas no effect unless -b option is also used; it has no effect on platforms other than MS-DOS and MS-Windows.
grep -u ...
-Z
Output a zero byte (the ASCII NUL character) instead of the character that normally follows a file name. For example, grep
grep -Z ...
-A
Print NUM lines of trailing context after matching lines. Places a line containing a group separator (--) between contiguousgroups of matches. With the -o or --only-matching option, this has no effect and a warning is given.
grep -A ...
-B
Print NUM lines of leading context before matching lines. Places a line containing a group separator (--) between contiguousgroups of matches. With the -o or --only-matching option, this has no effect and a warning is given.
grep -B ...
-C
Print NUM lines of output context. Places a line containing a group separator (--) between contiguous groups of matches.With the -o or --only-matching option, this has no effect and a warning is given.File and Directory Selection
grep -C ...
-a
Process a binary file as if it were text; this is equivalent to the --binary-files=text option.
grep -a ...
--binary-files
If a file's data or metadata indicate that the file contains binary data, assume that the file is of type TYPE. Non-textbytes indicate binary data; these are either output bytes that are improperly encoded for the current locale, or null inputbytes when the -z option is not given.By default, TYPE is binary, and when grep discovers that a file is binary it suppresses any further output, and insteadoutputs either a one-line message saying that a binary file matches, or no message if there is no match.If TYPE is without-match, when grep discovers that a file is binary it assumes that the rest of the file does not match; thisis equivalent to the -I option.If TYPE is text, grep processes a binary file as if it were text; this is equivalent to the -a option.When type is binary, grep may treat non-text bytes as line terminators even without the -z option. This means choosing binaryversus text can affect whether a pattern matches a file. For example, when type is binary the pattern q$ might match qimmediately followed by a null byte, even though this is not matched when type is text. Conversely, when type is binary thepattern . (period) might not match a null byte.Warning: The -a option might output binary garbage, which can have nasty side effects if the output is a terminal and if theterminal driver interprets some of it as commands. On the other hand, when reading files whose text encodings are unknown, itcan be helpful to use -a or to set LC_ALL='C' in the environment, in order to find more matches even if the matches are unsafefor direct display.
grep --binary-files ...
-D
If an input file is a device, FIFO or socket, use ACTION to process it. By default, ACTION is read, which means that devicesare read just as if they were ordinary files. If ACTION is skip, devices are silently skipped.
grep -D ...
-d
If an input file is a directory, use ACTION to process it. By default, ACTION is read, i.e., read directories just as if theywere ordinary files. If ACTION is skip, silently skip directories. If ACTION is recurse, read all files under eachdirectory, recursively, following symbolic links only if they are on the command line. This is equivalent to the -r option.
grep -d ...
--exclude
Skip any command-line file with a name suffix that matches the pattern GLOB, using wildcard matching; a name suffix is eitherthe whole name, or any suffix starting after a / and before a +non-/. When searching recursively, skip any subfile whose basename matches GLOB; the base name is the part after the last /. A pattern can use *, ?, and [...] as wildcards, and \ toquote a wildcard or backslash character literally.
grep --exclude ...
--exclude-from
Skip files whose base name matches any of the file-name globs read from FILE (using wildcard matching as described under
grep --exclude-from ...
--exclude-dir
Skip any command-line directory with a name suffix that matches the pattern GLOB. When searching recursively, skip anysubdirectory whose base name matches GLOB. Ignore any redundant trailing slashes in GLOB.
grep --exclude-dir ...
-I
Process a binary file as if it did not contain matching data; this is equivalent to the --binary-files=without-match option.
grep -I ...
--include
Search only files whose base name matches GLOB (using wildcard matching as described under --exclude).
grep --include ...
-r
Read all files under each directory, recursively, following symbolic links only if they are on the command line. Note that ifno file operand is given, grep searches the working directory. This is equivalent to the -d recurse option.
grep -r ...
-R
Read all files under each directory, recursively. Follow all symbolic links, unlike -r.Other Options
grep -R ...
--line-buffered
Use line buffering on output. This can cause a performance penalty.
grep --line-buffered ...
-U
Treat the file(s) as binary. By default, under MS-DOS and MS-Windows, grep guesses whether a file is text or binary asdescribed for the --binary-files option. If grep decides the file is a text file, it strips the CR characters from theoriginal file contents (to make regular expressions with ^ and $ work correctly). Specifying -U overrules this guesswork,causing all files to be read and passed to the matching mechanism verbatim; if the file is a text file with CR/LF pairs at theend of each line, this will cause some regular expressions to fail. This option has no effect on platforms other than MS-DOSand MS-Windows.
grep -U ...
-z
Treat input and output data as sequences of lines, each terminated by a zero byte (the ASCII NUL character) instead of anewline. Like the -Z or --null option, this option can be used with commands like sort -z to process arbitrary file names.REGULAR EXPRESSIONSA regular expression is a pattern that describes a set of strings. Regular expressions are constructed analogously to arithmeticexpressions, by using various operators to combine smaller expressions.grep understands three different versions of regular expression syntax: “basic” (BRE), “extended” (ERE) and “perl” (PCRE). In GNUgrep there is no difference in available functionality between basic and extended syntaxes. In other implementations, basic regularexpressions are less powerful. The following description applies to extended regular expressions; differences for basic regularexpressions are summarized afterwards. Perl-compatible regular expressions give additional functionality, and are documented inpcresyntax(3) and pcrepattern(3), but work only if PCRE is available in the system.The fundamental building blocks are the regular expressions that match a single character. Most characters, including all lettersand digits, are regular expressions that match themselves. Any meta-character with special meaning may be quoted by preceding itwith a backslash.The period . matches any single character.Character Classes and Bracket ExpressionsA bracket expression is a list of characters enclosed by [ and ]. It matches any single character in that list; if the firstcharacter of the list is the caret ^ then it matches any character not in the list. For example, the regular expression [0123456789]matches any single digit.Within a bracket expression, a range expression consists of two characters separated by a hyphen. It matches any single characterthat sorts between the two characters, inclusive, using the locale's collating sequence and character set. For example, in thedefault C locale, [a-d] is equivalent to [abcd]. Many locales sort characters in dictionary order, and in these locales [a-d] istypically not equivalent to [abcd]; it might be equivalent to [aBbCcDd], for example. To obtain the traditional interpretation ofbracket expressions, you can use the C locale by setting the LC_ALL environment variable to the value C.Finally, certain named classes of characters are predefined within bracket expressions, as follows. Their names are selfexplanatory, and they are [:alnum:], [:alpha:], [:cntrl:], [:digit:], [:graph:], [:lower:], [:print:], [:punct:], [:space:],[:upper:], and [:xdigit:]. For example, [[:alnum:]] means the character class of numbers and letters in the current locale. In theC locale and ASCII character set encoding, this is the same as [0-9A-Za-z]. (Note that the brackets in these class names are part ofthe symbolic names, and must be included in addition to the brackets delimiting the bracket expression.) Most meta-characters losetheir special meaning inside bracket expressions. To include a literal ] place it first in the list. Similarly, to include aliteral ^ place it anywhere but first. Finally, to include a literal - place it last.AnchoringThe caret ^ and the dollar sign $ are meta-characters that respectively match the empty string at the beginning and end of a line.The Backslash Character and Special ExpressionsThe symbols \< and \> respectively match the empty string at the beginning and end of a word. The symbol \b matches the empty stringat the edge of a word, and \B matches the empty string provided it's not at the edge of a word. The symbol \w is a synonym for[_[:alnum:]] and \W is a synonym for [^_[:alnum:]].RepetitionA regular expression may be followed by one of several repetition operators:? The preceding item is optional and matched at most once.* The preceding item will be matched zero or more times.+ The preceding item will be matched one or more times.{n} The preceding item is matched exactly n times.{n,} The preceding item is matched n or more times.{,m} The preceding item is matched at most m times. This is a GNU extension.{n,m} The preceding item is matched at least n times, but not more than m times.ConcatenationTwo regular expressions may be concatenated; the resulting regular expression matches any string formed by concatenating twosubstrings that respectively match the concatenated expressions.AlternationTwo regular expressions may be joined by the infix operator |; the resulting regular expression matches any string matching eitheralternate expression.PrecedenceRepetition takes precedence over concatenation, which in turn takes precedence over alternation. A whole expression may be enclosedin parentheses to override these precedence rules and form a subexpression.Back References and SubexpressionsThe back-reference \n, where n is a single digit, matches the substring previously matched by the nth parenthesized subexpression ofthe regular expression.Basic vs Extended Regular ExpressionsIn basic regular expressions the meta-characters ?, +, {, |, (, and ) lose their special meaning; instead use the backslashedversions \?, \+, \{, \|, \(, and \).ENVIRONMENT VARIABLESThe behavior of grep is affected by the following environment variables.The locale for category LC_foo is specified by examining the three environment variables LC_ALL, LC_foo, LANG, in that order. Thefirst of these variables that is set specifies the locale. For example, if LC_ALL is not set, but LC_MESSAGES is set to pt_BR, thenthe Brazilian Portuguese locale is used for the LC_MESSAGES category. The C locale is used if none of these environment variablesare set, if the locale catalog is not installed, or if grep was not compiled with national language support (NLS). The shell commandlocale -a lists locales that are currently available.GREP_OPTIONSThis variable specifies default options to be placed in front of any explicit options. As this causes problems when writingportable scripts, this feature will be removed in a future release of grep, and grep warns if it is used. Please use an aliasor script instead.GREP_COLORThis variable specifies the color used to highlight matched (non-empty) text. It is deprecated in favor of GREP_COLORS, butstill supported. The mt, ms, and mc capabilities of GREP_COLORS have priority over it. It can only specify the color used tohighlight the matching non-empty text in any matching line (a selected line when the -v command-line option is omitted, or acontext line when -v is specified). The default is 01;31, which means a bold red foreground text on the terminal's defaultbackground.GREP_COLORSSpecifies the colors and other attributes used to highlight various parts of the output. Its value is a colon-separated listof capabilities that defaults to ms=01;31:mc=01;31:sl=:cx=:fn=35:ln=32:bn=32:se=36 with the rv and ne boolean capabilitiesomitted (i.e., false). Supported capabilities are as follows.sl= SGR substring for whole selected lines (i.e., matching lines when the -v command-line option is omitted, or non-matching lines when -v is specified). If however the boolean rv capability and the -v command-line option are bothspecified, it applies to context matching lines instead. The default is empty (i.e., the terminal's default colorpair).cx= SGR substring for whole context lines (i.e., non-matching lines when the -v command-line option is omitted, or matchinglines when -v is specified). If however the boolean rv capability and the -v command-line option are both specified,it applies to selected non-matching lines instead. The default is empty (i.e., the terminal's default color pair).rv Boolean value that reverses (swaps) the meanings of the sl= and cx= capabilities when the -v command-line option isspecified. The default is false (i.e., the capability is omitted).mt=01;31SGR substring for matching non-empty text in any matching line (i.e., a selected line when the -v command-line optionis omitted, or a context line when -v is specified). Setting this is equivalent to setting both ms= and mc= at once tothe same value. The default is a bold red text foreground over the current line background.ms=01;31SGR substring for matching non-empty text in a selected line. (This is only used when the -v command-line option isomitted.) The effect of the sl= (or cx= if rv) capability remains active when this kicks in. The default is a boldred text foreground over the current line background.mc=01;31SGR substring for matching non-empty text in a context line. (This is only used when the -v command-line option isspecified.) The effect of the cx= (or sl= if rv) capability remains active when this kicks in. The default is a boldred text foreground over the current line background.fn=35 SGR substring for file names prefixing any content line. The default is a magenta text foreground over the terminal'sdefault background.ln=32 SGR substring for line numbers prefixing any content line. The default is a green text foreground over the terminal'sdefault background.bn=32 SGR substring for byte offsets prefixing any content line. The default is a green text foreground over the terminal'sdefault background.se=36 SGR substring for separators that are inserted between selected line fields (:), between context line fields, (-), andbetween groups of adjacent lines when nonzero context is specified (--). The default is a cyan text foreground overthe terminal's default background.ne Boolean value that prevents clearing to the end of line using Erase in Line (EL) to Right (\33[K) each time a colorizeditem ends. This is needed on terminals on which EL is not supported. It is otherwise useful on terminals for whichthe back_color_erase (bce) boolean terminfo capability does not apply, when the chosen highlight colors do not affectthe background, or when EL is too slow or causes too much flicker. The default is false (i.e., the capability isomitted).Note that boolean capabilities have no =... part. They are omitted (i.e., false) by default and become true when specified.See the Select Graphic Rendition (SGR) section in the documentation of the text terminal that is used for permitted values andtheir meaning as character attributes. These substring values are integers in decimal representation and can be concatenatedwith semicolons. grep takes care of assembling the result into a complete SGR sequence (\33[...m). Common values toconcatenate include 1 for bold, 4 for underline, 5 for blink, 7 for inverse, 39 for default foreground color, 30 to 37 forforeground colors, 90 to 97 for 16-color mode foreground colors, 38;5;0 to 38;5;255 for 88-color and 256-color modesforeground colors, 49 for default background color, 40 to 47 for background colors, 100 to 107 for 16-color mode backgroundcolors, and 48;5;0 to 48;5;255 for 88-color and 256-color modes background colors.LC_ALL, LC_COLLATE, LANGThese variables specify the locale for the LC_COLLATE category, which determines the collating sequence used to interpretrange expressions like [a-z].LC_ALL, LC_CTYPE, LANGThese variables specify the locale for the LC_CTYPE category, which determines the type of characters, e.g., which charactersare whitespace. This category also determines the character encoding, that is, whether text is encoded in UTF-8, ASCII, orsome other encoding. In the C or POSIX locale, all characters are encoded as a single byte and every byte is a validcharacter.LC_ALL, LC_MESSAGES, LANGThese variables specify the locale for the LC_MESSAGES category, which determines the language that grep uses for messages.The default C locale uses American English messages.POSIXLY_CORRECTIf set, grep behaves as POSIX requires; otherwise, grep behaves more like other GNU programs. POSIX requires that optionsthat follow file names must be treated as file names; by default, such options are permuted to the front of the operand listand are treated as options. Also, POSIX requires that unrecognized options be diagnosed as “illegal”, but since they are notreally against the law the default is to diagnose them as “invalid”. POSIXLY_CORRECT also disables_N_GNU_nonoption_argv_flags_, described below._N_GNU_nonoption_argv_flags_(Here N is grep's numeric process ID.) If the ith character of this environment variable's value is 1, do not consider theith operand of grep to be an option, even if it appears to be one. A shell can put this variable in the environment for eachcommand it runs, specifying which operands are the results of file name wildcard expansion and therefore should not be treatedas options. This behavior is available only with the GNU C library, and only when POSIXLY_CORRECT is not set.EXIT STATUSNormally the exit status is 0 if a line is selected, 1 if no lines were selected, and 2 if an error occurred. However, if the -q or
grep -z ...
--quiet
COPYRIGHTCopyright 1998–2000, 2002, 2005–2017 Free Software Foundation, Inc.This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR APARTICULAR PURPOSE.BUGSReporting BugsEmail bug reports to the bug-reporting address ⟨bug-grep@gnu.org⟩. An email archive ⟨http://lists.gnu.org/mailman/listinfo/bug-grep⟩and a bug tracker ⟨http://debbugs.gnu.org/cgi/pkgreport.cgi?package=grep⟩ are available.Known BugsLarge repetition counts in the {n,m} construct may cause grep to use lots of memory. In addition, certain other obscure regularexpressions require exponential time and space, and may cause grep to run out of memory.Back-references are very slow, and may require exponential time.
grep --quiet ...