Cum se utilizeaza „grep/egrep/fgrep” ?

Lista completa cu opțiuni le găsiți mai jos:

<br />NAME<br />       grep, egrep, fgrep - print lines matching a pattern<br /><br />SYNOPSIS<br />       grep [OPTIONS] PATTERN [FILE...]<br />       grep [OPTIONS] [-e PATTERN | -f FILE] [FILE...]<br /><br />DESCRIPTION<br />       grep  searches  the named input FILEs (or standard input if no files are named, or if a single hyphen-minus (-) is given as file name) for lines<br />       containing a match to the given PATTERN.  By default, grep prints the matching lines.<br /><br />       In addition, two variant programs egrep and fgrep are available.  egrep is the  same  as  grep -E.   fgrep  is  the  same  as  grep -F.   Direct<br />       invocation as either egrep or fgrep is deprecated, but is provided to allow historical applications that rely on them to run unmodified.<br /><br />OPTIONS<br />   Generic Program Information<br />       --help Print a usage message briefly summarizing these command-line options and the bug-reporting address, then exit.<br /><br />       -V, --version<br />              Print the version number of grep to the standard output stream.  This version number should be included in all bug reports (see below).<br /><br />   Matcher Selection<br />       -E, --extended-regexp<br />              Interpret PATTERN as an extended regular expression (ERE, see below).  (-E is specified by POSIX.)<br /><br />       -F, --fixed-strings<br />              Interpret PATTERN as a list of fixed strings, separated by newlines, any of which is to be matched.  (-F is specified by POSIX.)<br /><br />       -G, --basic-regexp<br />              Interpret PATTERN as a basic regular expression (BRE, see below).  This is the default.<br /><br />       -P, --perl-regexp<br />              Interpret PATTERN as a Perl regular expression.  This is highly experimental and grep -P may warn of unimplemented features.<br /><br />   Matching Control<br />       -e PATTERN, --regexp=PATTERN<br />              Use  PATTERN  as the pattern.  This can be used to specify multiple search patterns, or to protect a pattern beginning with a hyphen (-).<br />              (-e is specified by POSIX.)<br /><br />       -f FILE, --file=FILE<br />              Obtain patterns from FILE, one per line.  The empty file contains zero patterns, and therefore matches  nothing.   (-f  is  specified  by<br />              POSIX.)<br /><br />       -i, --ignore-case<br />              Ignore case distinctions in both the PATTERN and the input files.  (-i is specified by POSIX.)<br /><br />       -v, --invert-match<br />              Invert the sense of matching, to select non-matching lines.  (-v is specified by POSIX.)<br /><br />       -w, --word-regexp<br />              Select  only  those  lines  containing  matches  that  form  whole  words.  The test is that the matching substring must either be at the<br /><br />        -x, --line-regexp<br />              Select only those matches that exactly match the whole line.  (-x is specified by POSIX.)<br /><br />       -y     Obsolete synonym for -i.<br /><br />   General Output Control<br />       -c, --count<br />              Suppress  normal  output;  instead  print a count of matching lines for each input file.  With the -v, --invert-match option (see below),<br />              count non-matching lines.  (-c is specified by POSIX.)<br /><br />       --color[=WHEN], --colour[=WHEN]<br />              Surround the matched (non-empty) strings, matching lines, context lines, file names, line numbers,  byte  offsets,  and  separators  (for<br />              fields  and  groups  of  context  lines)  with  escape sequences to display them in color on the terminal.  The colors are defined by the<br />              environment variable GREP_COLORS.  The deprecated environment variable GREP_COLOR is still supported,  but  its  setting  does  not  have<br />              priority.  WHEN is never, always, or auto.<br /><br />       -L, --files-without-match<br />              Suppress  normal  output;  instead print the name of each input file from which no output would normally have been printed.  The scanning<br />              will stop on the first match.<br /><br />       -l, --files-with-matches<br />              Suppress normal output; instead print the name of each input file from which output would normally have been printed.  The scanning  will<br />              stop on the first match.  (-l is specified by POSIX.)<br /><br />       -m NUM, --max-count=NUM<br />              Stop  reading  a  file  after NUM matching lines.  If the input is standard input from a regular file, and NUM matching lines are output,<br />              grep ensures that the standard input is positioned to just after the last matching line before exiting, regardless  of  the  presence  of<br />              trailing  context  lines.   This  enables a calling process to resume a search.  When grep stops after NUM matching lines, it outputs any<br />              trailing context lines.  When the -c or --count option is also used, grep does not output a count greater  than  NUM.   When  the  -v  or<br />              --invert-match option is also used, grep stops after outputting NUM non-matching lines.<br /><br />       -o, --only-matching<br />              Print only the matched (non-empty) parts of a matching line, with each such part on a separate output line.<br /><br />       -q, --quiet, --silent<br />              Quiet; do not write anything to standard output.  Exit immediately with zero status if any match is found, even if an error was detected.<br />              Also see the -s or --no-messages option.  (-q is specified by POSIX.)<br /><br />       -s, --no-messages<br />              Suppress error messages about nonexistent or unreadable files.  Portability note: unlike GNU grep, 7th Edition Unix grep did not  conform<br />              to  POSIX,  because  it  lacked  -q and its -s option behaved like GNU grep's -q option.  USG-style grep also lacked -q but its -s option<br />              behaved like GNU grep.  Portable shell scripts should avoid both -q and -s and should redirect standard and  error  output  to  /dev/null<br />              instead.  (-s is specified by POSIX.)<br />   Output Line Prefix Control<br />       -b, --byte-offset<br />              Print  the  0-based byte offset within the input file before each line of output.  If -o (--only-matching) is specified, print the offset<br />              of the matching part itself.<br /><br />       -H, --with-filename<br />              Print the file name for each match.  This is the default when there is more than one file to search.<br /><br />       -h, --no-filename<br />              Suppress the prefixing of file names on output.  This is the default when there is only one file (or only standard input) to search.<br /><br />       --label=LABEL<br />              Display input actually coming from standard input as input coming from file LABEL.  This is especially useful for tools like zgrep, e.g.,<br />              gzip -cd foo.gz | grep --label=foo something<br /><br />       -n, --line-number<br />              Prefix each line of output with the 1-based line number within its input file.  (-n is specified by POSIX.)<br /><br />       -T, --initial-tab<br />              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<br />              with options that prefix their output to the actual content: -H,-n, and -b.  In order to improve the probability that lines from a single<br />              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<br />              field width.<br /><br />       -u, --unix-byte-offsets<br />              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<br />              characters  stripped  off.   This  will produce results identical to running grep on a Unix machine.  This option has no effect unless -b<br />              option is also used; it has no effect on platforms other than MS-DOS and MS-Windows.<br /><br />       -Z, --null<br />              Output a zero byte (the ASCII NUL character) instead of the character that normally follows a file name.  For example, grep -lZ outputs a<br />              zero  byte  after  each  file  name instead of the usual newline.  This option makes the output unambiguous, even in the presence of file<br />              names containing unusual characters like newlines.  This option can be used with commands like find -print0, perl -0, sort -z, and  xargs<br />              -0 to process arbitrary file names, even those that contain newline characters.<br /><br />   Context Line Control<br />       -A NUM, --after-context=NUM<br />              Print  NUM  lines of trailing context after matching lines.  Places a line containing a group separator (--) between contiguous groups of<br />              matches.  With the -o or --only-matching option, this has no effect and a warning is given.<br /><br />       -B NUM, --before-context=NUM<br />              Print NUM lines of leading context before matching lines.  Places a line containing a group separator (--) between contiguous  groups  of<br />              matches.  With the -o or --only-matching option, this has no effect and a warning is given.<br /><br />       -C NUM, -NUM, --context=NUM<br />              Print NUM lines of output context.  Places a line containing a group separator (--) between contiguous groups of matches.  With the -o or<br />              --only-matching option, this has no effect and a warning is given.<br /><br /> File and Directory Selection<br />       -a, --text<br />              Process a binary file as if it were text; this is equivalent to the --binary-files=text option.<br /><br />       --binary-files=TYPE<br />              If the first few bytes of a file indicate that the file contains binary data, assume that the file is of type TYPE.  By default, TYPE  is<br />              binary,  and  grep  normally outputs either a one-line message saying that a binary file matches, or no message if there is no match.  If<br />              TYPE is without-match, grep assumes that a binary file does not match; this is equivalent to the  -I  option.   If  TYPE  is  text,  grep<br />              processes  a  binary file as if it were text; this is equivalent to the -a option.  Warning: grep --binary-files=text might output binary<br />              garbage, which can have nasty side effects if the output is a terminal and if the terminal driver interprets some of it as commands.<br /><br />       -D ACTION, --devices=ACTION<br />              If an input file is a device, FIFO or socket, use ACTION to process it.  By default, ACTION is read, which means that  devices  are  read<br />              just as if they were ordinary files.  If ACTION is skip, devices are silently skipped.<br /><br />       -d ACTION, --directories=ACTION<br />              If  an input file is a directory, use ACTION to process it.  By default, ACTION is read, which means that directories are read just as if<br />              they were ordinary files.  If ACTION is skip, directories are silently skipped.  If ACTION is recurse, grep reads all  files  under  each<br />              directory, recursively; this is equivalent to the -r option.<br /><br />       --exclude=GLOB<br />              Skip  files  whose  base  name  matches GLOB (using wildcard matching).  A file-name glob can use *, ?, and [...]  as wildcards, and  to<br />              quote a wildcard or backslash character literally.<br /><br />       --exclude-from=FILE<br />              Skip files whose base name matches any of the file-name globs read from FILE (using wildcard matching as described under --exclude).<br /><br />       --exclude-dir=DIR<br />              Exclude directories matching the pattern DIR from recursive searches.<br /><br />       -I     Process a binary file as if it did not contain matching data; this is equivalent to the --binary-files=without-match option.<br /><br />       --include=GLOB<br />              Search only files whose base name matches GLOB (using wildcard matching as described under --exclude).<br /><br />       -R, -r, --recursive<br />   Other Options<br />       --line-buffered<br />              Use line buffering on output.  This can cause a performance penalty.<br /><br />       --mmap If possible, use the mmap(2) system call to read input, instead of the default read(2) system call.  In some  situations,  --mmap  yields<br />              better  performance.   However,  --mmap  can  cause  undefined  behavior  (including  core  dumps) if an input file shrinks while grep is<br />              operating, or if an I/O error occurs.<br /><br />       -U, --binary<br />              Treat the file(s) as binary.  By default, under MS-DOS and MS-Windows, grep guesses the file type by looking at the contents of the first<br />              32KB  read  from the file.  If grep decides the file is a text file, it strips the CR characters from the original file contents (to make<br />              regular expressions with ^ and $ work correctly).  Specifying -U overrules this guesswork, causing all files to be read and passed to the<br />              matching  mechanism  verbatim;  if  the  file  is  a  text  file  with  CR/LF pairs at the end of each line, this will cause some regular<br />              expressions to fail.  This option has no effect on platforms other than MS-DOS and MS-Windows.<br /><br />       -z, --null-data<br />              Treat the input as a set of lines, each terminated by a zero byte (the ASCII NUL character) instead of a newline.  Like the -Z or  --null<br />              option, this option can be used with commands like sort -z to process arbitrary file names.<br /><br />REGULAR EXPRESSIONS<br />       A  regular  expression is a pattern that describes a set of strings.  Regular expressions are constructed analogously to arithmetic expressions,<br />       by using various operators to combine smaller expressions.<br /><br />       grep understands two different versions of regular expression syntax: "basic" and "extended."  In GNU grep, there is no difference in  available<br />       functionality using either syntax.  In other implementations, basic regular expressions are less powerful.  The following description applies to<br />       extended regular expressions; differences for basic regular expressions are summarized afterwards.<br /><br />       The fundamental building blocks are the regular expressions that match a single character.  Most characters, including all letters  and  digits,<br />       are regular expressions that match themselves.  Any meta-character with special meaning may be quoted by preceding it with a backslash.<br /><br />       The period . matches any single character.<br /><br />   Character Classes and Bracket Expressions<br />       A  bracket  expression is a list of characters enclosed by [ and ].  It matches any single character in that list; if the first character of the<br />       list is the caret ^ then it matches any character not in the list.  For example, the regular expression [0123456789] matches any single digit.<br /><br />       Within a bracket expression, a range expression consists of two characters separated by a hyphen.  It matches any single  character  that  sorts<br />       between  the two characters, inclusive, using the locale's collating sequence and character set.  For example, in the default C locale, [a-d] is<br />       equivalent to [abcd].  Many locales sort characters in dictionary order, and in these locales [a-d] is typically not equivalent  to  [abcd];  it<br />       might  be  equivalent  to  [aBbCcDd], for example.  To obtain the traditional interpretation of bracket expressions, you can use the C locale by<br />       setting the LC_ALL environment variable to the value C.<br /><br />       Finally, certain named classes of characters are predefined within bracket expressions, as follows.  Their names are self explanatory, and  they<br />       are  [:alnum:], [:alpha:], [:cntrl:], [:digit:], [:graph:], [:lower:], [:print:], [:punct:], [:space:], [:upper:], and [:xdigit:].  For example,<br />       [[:alnum:]] means [0-9A-Za-z], except the latter form depends upon the C locale  and  the  ASCII  character  encoding,  whereas  the  former  is<br />       independent  of  locale and character set.  (Note that the brackets in these class names are part of the symbolic names, and must be included in<br />       addition to the brackets delimiting the bracket expression.)  Most meta-characters lose their special meaning inside  bracket  expressions.   To<br />       include a literal ] place it first in the list.  Similarly, to include a literal ^ place it anywhere but first.  Finally, to include a literal -<br />       place it last.<br /> Anchoring<br />       The caret ^ and the dollar sign $ are meta-characters that respectively match the empty string at the beginning and end of a line.<br /><br />   The Backslash Character and Special Expressions<br />       The symbols < and > respectively match the empty string at the beginning and end of a word.  The symbol b matches the  empty  string  at  the<br />       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<br />       synonym for [^[:alnum:]].<br /><br />   Repetition<br />       A regular expression may be followed by one of several repetition operators:<br />       ?      The preceding item is optional and matched at most once.<br />       *      The preceding item will be matched zero or more times.<br />       +      The preceding item will be matched one or more times.<br />       {n}    The preceding item is matched exactly n times.<br />       {n,}   The preceding item is matched n or more times.<br />       {,m}   The preceding item is matched at most m times.<br />       {n,m}  The preceding item is matched at least n times, but not more than m times.<br /><br />   Concatenation<br />       Two regular expressions may be concatenated; the resulting regular expression matches any string formed by  concatenating  two  substrings  that<br />       respectively match the concatenated expressions.<br /><br />   Alternation<br />       Two  regular  expressions  may  be joined by the infix operator |; the resulting regular expression matches any string matching either alternate<br />       expression.<br /><br />   Precedence<br />       Repetition takes precedence over concatenation, which in turn takes precedence  over  alternation.   A  whole  expression  may  be  enclosed  in<br />       parentheses to override these precedence rules and form a subexpression.<br /><br />   Back References and Subexpressions<br />       The back-reference n, where n is a single digit, matches the substring previously matched by the nth parenthesized subexpression of the regular<br />       expression.<br /><br />   Basic vs Extended Regular Expressions<br />       In basic regular expressions the meta-characters ?, +, {, |, (, and ) lose their special meaning; instead use the backslashed versions  ?,  +,<br />       {, |, (, and ).<br /><br />       Traditional egrep did not support the { meta-character, and some egrep implementations support { instead, so portable scripts should avoid { in<br />       grep -E patterns and should use [{] to match a literal {.<br /><br />       GNU grep -E attempts to support traditional usage by assuming that {  is  not  special  if  it  would  be  the  start  of  an  invalid  interval<br />       specification.   For  example,  the  command  grep -E '{1'  searches  for the two-character string {1 instead of reporting a syntax error in the<br />       regular expression.  POSIX.2 allows this behavior as an extension, but portable scripts should avoid it.<br />ENVIRONMENT VARIABLES<br />       The behavior of grep is affected by the following environment variables.<br /><br />       The locale for category LC_foo is specified by examining the three environment variables LC_ALL, LC_foo, LANG, in  that  order.   The  first  of<br />       these  variables  that  is  set  specifies  the  locale.  For example, if LC_ALL is not set, but LC_MESSAGES is set to pt_BR, then the Brazilian<br />       Portuguese locale is used for the LC_MESSAGES category.  The C locale is used if none of these environment variables  are  set,  if  the  locale<br />       catalog is not installed, or if grep was not compiled with national language support (NLS).<br /><br />       GREP_OPTIONS<br />              This  variable  specifies  default  options  to  be  placed in front of any explicit options.  For example, if GREP_OPTIONS is '--binary-<br />              files=without-match --directories=skip', grep behaves as if the two options --binary-files=without-match and --directories=skip had  been<br />              specified before any explicit options.  Option specifications are separated by whitespace.  A backslash escapes the next character, so it<br />              can be used to specify an option containing whitespace or a backslash.<br /><br />       GREP_COLOR<br />              This variable specifies the color used to highlight matched (non-empty) text.  It is  deprecated  in  favor  of  GREP_COLORS,  but  still<br />              supported.   The  mt,  ms, and mc capabilities of GREP_COLORS have priority over it.  It can only specify the color used to highlight the<br />              matching non-empty text in any matching line (a selected line when the -v command-line option is omitted, or a context line  when  -v  is<br />              specified).  The default is 01;31, which means a bold red foreground text on the terminal's default background.<br /><br />       GREP_COLORS<br />              Specifies  the  colors  and  other  attributes  used  to  highlight  various parts of the output.  Its value is a colon-separated list of<br />              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  capabilities  omitted  (i.e.,<br />              false).  Supported capabilities are as follows.<br /><br />              sl=    SGR  substring  for  whole  selected lines (i.e., matching lines when the -v command-line option is omitted, or non-matching lines<br />                     when -v is specified).  If however the boolean rv capability and the -v command-line option are  both  specified,  it  applies  to<br />                     context matching lines instead.  The default is empty (i.e., the terminal's default color pair).<br /><br />              cx=    SGR substring for whole context lines (i.e., non-matching lines when the -v command-line option is omitted, or matching lines when<br />                     -v is specified).  If however the boolean rv capability and the -v command-line option are both specified, it applies to  selected<br />                     non-matching lines instead.  The default is empty (i.e., the terminal's default color pair).<br /><br />              rv     Boolean  value  that  reverses  (swaps) the meanings of the sl= and cx= capabilities when the -v command-line option is specified.<br />                     The default is false (i.e., the capability is omitted).<br /><br />              mt=01;31<br />                     SGR substring for matching non-empty text in any matching line (i.e., a selected line when the -v command-line option is  omitted,<br />                     or  a  context line when -v is specified).  Setting this is equivalent to setting both ms= and mc= at once to the same value.  The<br />                     default is a bold red text foreground over the current line background.<br /><br />              ms=01;31<br />                     SGR substring for matching non-empty text in a selected line.  (This is only used when the -v  command-line  option  is  omitted.)<br />                     The effect of the sl= (or cx= if rv) capability remains active when this kicks in.  The default is a bold red text foreground over<br />                     the current line background.<br /><br />              mc=01;31<br />                     SGR substring for matching non-empty text in a context line.  (This is only used when the -v command-line  option  is  specified.)<br />                     The effect of the cx= (or sl= if rv) capability remains active when this kicks in.  The default is a bold red text foreground over<br />                     the current line background.<br /><br />              fn=35  SGR substring for file names prefixing any content line.  The default is a magenta text foreground  over  the  terminal's  default<br />                     background.<br />              ln=32  SGR  substring  for  line  numbers prefixing any content line.  The default is a green text foreground over the terminal's default<br />                     background.<br /><br />              bn=32  SGR substring for byte offsets prefixing any content line.  The default is a green text foreground  over  the  terminal's  default<br />                     background.<br /><br />              se=36  SGR  substring  for  separators  that are inserted between selected line fields (:), between context line fields, (-), and between<br />                     groups of adjacent lines when nonzero context is specified (--).  The default is  a  cyan  text  foreground  over  the  terminal's<br />                     default background.<br /><br />              ne     Boolean value that prevents clearing to the end of line using Erase in Line (EL) to Right (33[K) each time a colorized item ends.<br />                     This is needed on terminals on which EL is not supported.  It is otherwise useful on  terminals  for  which  the  back_color_erase<br />                     (bce) boolean terminfo capability does not apply, when the chosen highlight colors do not affect the background, or when EL is too<br />                     slow or causes too much flicker.  The default is false (i.e., the capability is omitted).<br /><br />              Note that boolean capabilities have no =...  part.  They are omitted (i.e., false) by default and become true when specified.<br /><br />              See the Select Graphic Rendition (SGR) section in the documentation of the text terminal that is used  for  permitted  values  and  their<br />              meaning  as character attributes.  These substring values are integers in decimal representation and can be concatenated with semicolons.<br />              grep takes care of assembling the result into a complete SGR sequence (33[...m).  Common values to concatenate include 1 for bold, 4 for<br />              underline,  5  for  blink,  7  for  inverse,  39 for default foreground color, 30 to 37 for foreground colors, 90 to 97 for 16-color mode<br />              foreground colors, 38;5;0 to 38;5;255 for 88-color and 256-color modes foreground colors, 49 for default background color, 40 to  47  for<br />              background  colors,  100  to  107 for 16-color mode background colors, and 48;5;0 to 48;5;255 for 88-color and 256-color modes background<br />              colors.<br /><br />       LC_ALL, LC_COLLATE, LANG<br />              These variables specify the locale for the LC_COLLATE  category,  which  determines  the  collating  sequence  used  to  interpret  range<br />              expressions like [a-z].<br /><br />       LC_ALL, LC_CTYPE, LANG<br />              These  variables  specify  the  locale  for  the  LC_CTYPE  category, which determines the type of characters, e.g., which characters are<br />              whitespace.<br /><br />       LC_ALL, LC_MESSAGES, LANG<br />              These variables specify the locale for the LC_MESSAGES category, which determines the language that grep uses for messages.  The  default<br />              C locale uses American English messages.<br /><br />       POSIXLY_CORRECT<br />              If  set,  grep  behaves  as  POSIX.2  requires; otherwise, grep behaves more like other GNU programs.  POSIX.2 requires that options that<br />              follow file names must be treated as file names; by default, such options are permuted to the front of the operand list and  are  treated<br />              as  options.   Also,  POSIX.2 requires that unrecognized options be diagnosed as "illegal", but since they are not really against the law<br />              the default is to diagnose them as "invalid".  POSIXLY_CORRECT also disables _N_GNU_nonoption_argv_flags_, described below.<br /><br />       _N_GNU_nonoption_argv_flags_<br />              (Here N is grep's numeric process ID.)  If the ith character of this environment variable's value is 1, do not consider the  ith  operand<br />              of  grep  to  be  an  option,  even  if it appears to be one.  A shell can put this variable in the environment for each command it runs,<br />              specifying which operands are the results of file name wildcard expansion and therefore should not be treated as options.  This  behavior<br />              is available only with the GNU C library, and only when POSIXLY_CORRECT is not set.<br /><br />EXIT STATUS<br />       Normally,  the  exit  status  is 0 if selected lines are found and 1 otherwise.  But the exit status is 2 if an error occurred, unless the -q or<br />       --quiet or --silent option is used and a selected line is found.  Note, however, that POSIX only mandates, for programs such as grep,  cmp,  and<br />       diff,  that  the exit status in case of error be greater than 1; it is therefore advisable, for the sake of portability, to use logic that tests<br />       for this general condition instead of strict equality with 2.<br /><br />COPYRIGHT<br />       Copyright ▒ 1998, 1999, 2000, 2002, 2005 Free Software Foundation, Inc.<br /><br />       This is free software; see the source for copying conditions.  There is NO warranty; not even for MERCHANTABILITY or FITNESS  FOR  A  PARTICULAR<br />       PURPOSE.<br /><br />BUGS<br />   Reporting Bugs<br />       Email bug reports to  gnu.org, a mailing list whose web page is bug-grep lists.gnu.org.  grep's Savannah bug<br />       tracker is located at savannah.gnu.org.<br /><br />   Known Bugs<br />       Large repetition counts in the {n,m} construct may cause grep to use lots of memory.  In addition, certain  other  obscure  regular  expressions<br />       require exponential time and space, and may cause grep to run out of memory.<br /><br />       Back-references are very slow, and may require exponential time.<br /><br />SEE ALSO<br />   Regular Manual Pages<br />       awk(1), cmp(1), diff(1), find(1), gzip(1), perl(1), sed(1), sort(1), xargs(1), zgrep(1), mmap(2), read(2), pcre(3), pcrepattern(3), terminfo(5),<br />       glob(7), regex(7).<br /><br />   POSIX Programmer's Manual Page<br />       grep(1p).<br /><br />   TeXinfo Documentation<br />       The full documentation for grep is maintained as a TeXinfo manual.  If the info and grep programs are  properly  installed  at  your  site,  the<br />       command<br /><br />              info grep<br /><br />       should give you access to the complete manual.<br />