te
Copyright 1989 AT&T
Copyright (c) 2006, Sun Microsystems, Inc. All Rights Reserved
Portions Copyright (c) 1992, X/Open Company Limited All Rights Reserved
Sun Microsystems, Inc. gratefully acknowledges The Open Group for permission to reproduce portions of its copyrighted documentation. Original documentation from The Open Group can be obtained online at
http://www.opengroup.org/bookstore/.
The Institute of Electrical and Electronics Engineers and The Open Group, have given us permission to reprint portions of their documentation. In the following statement, the phrase "this text" refers to portions of the system documentation. Portions of this text are reprinted and reproduced in electronic form in the Sun OS Reference Manual, from IEEE Std 1003.1, 2004 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between these versions and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html.
This notice shall appear on any product containing this material.
The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
EGREP 1 "May 3, 2013"
NAME
egrep - search a file for a pattern using full regular expressions
SYNOPSIS

/usr/bin/egrep [-bcHhilnqsv] -e pattern_list [file...]

/usr/bin/egrep [-bcHhilnqsv] -f file [file...]

/usr/bin/egrep [-bcHhilnqsv] pattern [file...]

/usr/xpg4/bin/egrep [-bcHhilnqsvx] -e pattern_list [-f file]
 [file...]

/usr/xpg4/bin/egrep [-bcHhilnqsvx] [-e pattern_list] -f file
 [file...]

/usr/xpg4/bin/egrep [-bcHhilnqsvx] pattern [file...]
DESCRIPTION

The egrep (expression grep) utility searches files for a pattern of characters and prints all lines that contain that pattern. egrep uses full regular expressions (expressions that have string values that use the full set of alphanumeric and special characters) to match the patterns. It uses a fast deterministic algorithm that sometimes needs exponential space.

If no files are specified, egrep assumes standard input. Normally, each line found is copied to the standard output. The file name is printed before each line found if there is more than one input file.

The /usr/bin/egrep utility accepts full regular expressions as described on the regexp(5) manual page, except for \e( and \e), \e( and \e), \e{ and \e}, \e< and \e>, and \en, and with the addition of:

1. A full regular expression followed by + that matches one or more occurrences of the full regular expression.

2. A full regular expression followed by ? that matches 0 or 1 occurrences of the full regular expression.

3. Full regular expressions separated by | or by a NEWLINE that match strings that are matched by any of the expressions.

4. A full regular expression that can be enclosed in parentheses ()for grouping.

Be careful using the characters $, *, [, ^, |, (, ), and \e in full regular expression, because they are also meaningful to the shell. It is safest to enclose the entire full regular expression in single quotes (a\'a\').

The order of precedence of operators is [\|], then *\|?\|+, then concatenation, then | and NEWLINE.

The /usr/xpg4/bin/egrep utility uses the regular expressions described in the EXTENDED REGULAR EXPRESSIONS section of the regex(5) manual page.

OPTIONS

The following options are supported for both /usr/bin/egrep and /usr/xpg4/bin/egrep: -b

Precede each line by the block number on which it was found. This can be useful in locating block numbers by context (first block is 0).

-c

Print only a count of the lines that contain the pattern.

-e pattern_list

Search for a pattern_list (full regular expression that begins with a -).

-f file

Take the list of full regular expressions from file.

-H

Precedes each line by the name of the file containing the matching line.

-h

Suppress printing of filenames when searching multiple files.

-i

Ignore upper/lower case distinction during comparisons.

-l

Print the names of files with matching lines once, separated by NEWLINEs. Does not repeat the names of files when the pattern is found more than once.

-n

Precede each line by its line number in the file (first line is 1).

-q

Quiet. Does not write anything to the standard output, regardless of matching lines. Exits with zero status if an input line is selected.

-s

Legacy equivalent of -q.

-v

Print all lines except those that contain the pattern.

The following options are supported for /usr/xpg4/bin/egrep only: -x

Consider only input lines that use all characters in the line to match an entire fixed string or regular expression to be matching lines.

OPERANDS

The following operands are supported: file

A path name of a file to be searched for the patterns. If no file operands are specified, the standard input is used.

pattern

Specify a pattern to be used during the search for input.

pattern

Specify one or more patterns to be used during the search for input. This operand is treated as if it were specified as -epattern_list..

USAGE

See largefile(5) for the description of the behavior of egrep when encountering files greater than or equal to 2 Gbyte ( 2^31 bytes).

ENVIRONMENT VARIABLES

See environ(5) for descriptions of the following environment variables that affect the execution of egrep: LC_COLLATE, LC_CTYPE, LC_MESSAGES, and NLSPATH.

EXIT STATUS

The following exit values are returned: 0

If any matches are found.

1

If no matches are found.

2

For syntax errors or inaccessible files (even if matches were found).

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE ATTRIBUTE VALUE
CSI Not Enabled
ATTRIBUTE TYPE ATTRIBUTE VALUE
CSI Enabled
SEE ALSO

fgrep(1), grep(1), sed(1), sh(1), attributes(5), environ(5), largefile(5), regex(5), regexp(5), XPG4(5)

NOTES

Ideally there should be only one grep command, but there is not a single algorithm that spans a wide enough range of space-time trade-offs.

Lines are limited only by the size of the available virtual memory.

The /usr/xpg4/bin/egrep utility is identical to /usr/xpg4/bin/grep -E. See grep(1). Portable applications should use /usr/xpg4/bin/grep -E.