Differences between revisions 9 and 20 (spanning 11 versions)
Revision 9 as of 2008-06-04 06:29:41
Size: 2458
Editor: pgas
Comment: remove the useless awk example, use simpler good exemple, all this imho
Revision 20 as of 2011-04-14 13:04:43
Size: 3781
Comment: Ordinary grep supports pipe if escaped
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
[[Anchor(faq79)]] <<Anchor(faq79)>>
Line 3: Line 3:
This is really three different questions, so we'll break this answer into three parts.

=== foo AND bar on the same line ===
Line 17: Line 20:
If you prefer, you can achieve this in one {{{sed}}} or {{{awk}}} statement. (The {{{awk}}} example is probably the most scalable.) If you prefer, you can achieve this in one {{{sed}}} or {{{awk}}} statement:
Line 24: Line 27:
To match lines containing foo OR bar, {{{egrep}}} is the natural choice, but it can also be done with {{{sed}}}, {{{awk}}}, etc. If you need to scale the awk solution to an arbitrary number of patterns, you can construct the awk command on the fly:

{{{
# bash, ksh93
# Constructs awk "/$1/&&/$2/&&...."
# Data to be matched should be on stdin.
# Writes matching lines to stdout.
multimatch() {
  (($# < 2)) && { echo "usage: multimatch pat1 pat2 [...]" >&2; return 1; }
  awk "/$1/$(printf "&&/%s/" "${@:2}")"
}
}}}

Or, POSIX version:
{{{
# POSIX
multimatch() {
  [ $# -lt 2 ] && { echo "usage: multimatch pat1 pat2 [...]" >&2; return 1; }
  __p1=$1
  shift
  awk "/$__p1/$(printf "&&/%s/" "$@")"
}
}}}

Alas, POSIX functions do not have local variables. Also, both of these fail if any of the patterns contain slash characters. (Fixing that is left as an exercise for the reader.)

A POSIX version that doesn't embed the regexes into the awk script.
{{{
# POSIX
multimatch() {
  awk 'BEGIN{for(i=1;i<ARGC;i++) a[i]=ARGV[i]; ARGC=1} {for (i in a) if ($0 !~ a[i]) next; print}' "$@"
}
}}}

=== foo OR bar on the same line ===

There are lots of ways to match lines containing foo OR bar. `grep` can be given multiple patterns with `-e`:

{{{
grep -e 'foo' -e 'bar'
}}}

Or you can use the pipe character if escaped:

{{{
grep 'foo\|bar'
}}}

Or you can construct patterns with {{{egrep}}} (or `grep -E`):
Line 28: Line 79:
# some people prefer grep -E 'foo|bar' grep -E 'foo|bar'
}}}
Line 30: Line 82:
# This is another option, some people prefer:
grep -e 'foo' -e 'bar'
It can also be done with {{{sed}}}, {{{awk}}}, etc.
Line 33: Line 84:
# awk equivalent (eg if you want to extract fields) {{{
Line 37: Line 88:
{{{egrep}}} is the oldest and most portable form of the {{{grep}}} command using [:RegularExpression:Extended Regular Expressions (EREs)]. {{{grep -E}}} is required by POSIX. The `awk` approach has the advantage of letting you use `awk`'s other features on the matched lines, such as extracting only certain fields.

To match lines that do not contain "foo" AND do not contain "bar":

{{{
grep -E -v 'foo|bar'
# some people prefer egrep -v 'foo|bar'
}}}

=== foo AND bar in the same file, not necessarily on the same line ===
Line 44: Line 104:
Line 47: Line 106:
Another approach is to read the file once, keeping track of what you've seen as you go along. There are several ways to do this, for instance in awk: Another approach is to read the file once, keeping track of what you've seen as you go along. In awk:
Line 50: Line 109:
 awk '/foo/{a=1} /bar/{b=1} a&&b{print "both found";exit} END{if (a&&b){ exit 0} else{exit 1}}' awk '/foo/{a=1} /bar/{b=1} a&&b{print "both found";exit} END{if (a&&b){ exit 0} else{exit 1}}'
Line 52: Line 111:
It reads the file one time, stopping when both patterns have been matched. No matter what happens, the END block is then executed, and the exit status is set accordingly.
Line 53: Line 113:
It reads the file one time, stopping when both pattern have been matched, not matter what happens the END block is then executed
and the exit status is set accordingly.

If you want to do additional checking of the file contents, the awk solution can be adapted far more readily.
If you want to do additional checking of the file's contents, this awk solution can be adapted quite easily.

How can I grep for lines containing foo AND bar, foo OR bar? Or for files containing foo AND bar, possibly on separate lines?

This is really three different questions, so we'll break this answer into three parts.

foo AND bar on the same line

The easiest way to match lines that contain both foo AND bar is to use two grep commands:

grep foo | grep bar
grep foo "$myfile" | grep bar   # for those who need the hand-holding

It can also be done with one egrep, although (as you can probably guess) this doesn't really scale well to more than two patterns:

egrep 'foo.*bar|bar.*foo'

If you prefer, you can achieve this in one sed or awk statement:

sed -n '/foo/{/bar/p}'
awk '/foo/ && /bar/'

If you need to scale the awk solution to an arbitrary number of patterns, you can construct the awk command on the fly:

# bash, ksh93
# Constructs awk "/$1/&&/$2/&&...."
# Data to be matched should be on stdin.
# Writes matching lines to stdout.
multimatch() {
  (($# < 2)) && { echo "usage: multimatch pat1 pat2 [...]" >&2; return 1; }
  awk "/$1/$(printf "&&/%s/" "${@:2}")"
}

Or, POSIX version:

# POSIX
multimatch() {
  [ $# -lt 2 ] && { echo "usage: multimatch pat1 pat2 [...]" >&2; return 1; }
  __p1=$1
  shift
  awk "/$__p1/$(printf "&&/%s/" "$@")"
}

Alas, POSIX functions do not have local variables. Also, both of these fail if any of the patterns contain slash characters. (Fixing that is left as an exercise for the reader.)

A POSIX version that doesn't embed the regexes into the awk script.

# POSIX
multimatch() { 
  awk 'BEGIN{for(i=1;i<ARGC;i++) a[i]=ARGV[i]; ARGC=1} {for (i in a) if ($0 !~ a[i]) next; print}' "$@"
}

foo OR bar on the same line

There are lots of ways to match lines containing foo OR bar. grep can be given multiple patterns with -e:

grep -e 'foo' -e 'bar'

Or you can use the pipe character if escaped:

grep 'foo\|bar'

Or you can construct patterns with egrep (or grep -E):

egrep 'foo|bar'
grep -E 'foo|bar'

It can also be done with sed, awk, etc.

awk '/foo|bar/'

The awk approach has the advantage of letting you use awk's other features on the matched lines, such as extracting only certain fields.

To match lines that do not contain "foo" AND do not contain "bar":

grep -E -v 'foo|bar'
# some people prefer egrep -v 'foo|bar'

foo AND bar in the same file, not necessarily on the same line

If you want to match files (rather than lines) that contain both "foo" and "bar", there are several possible approaches. The simplest (although not necessarily the most efficient) is to read the file twice:

grep -q foo "$myfile" && grep -q bar "$myfile" && echo "Found both"

The double grep -q solution has the advantage of stopping each read whenever it finds a match; so if you have a huge file, but the matched words are both near the top, it will only read the first part of the file. Unfortunately, if the matches are near the bottom (worst case: very last line of the file), you may read the whole file two times.

Another approach is to read the file once, keeping track of what you've seen as you go along. In awk:

awk '/foo/{a=1} /bar/{b=1} a&&b{print "both found";exit} END{if (a&&b){ exit 0} else{exit 1}}'

It reads the file one time, stopping when both patterns have been matched. No matter what happens, the END block is then executed, and the exit status is set accordingly.

If you want to do additional checking of the file's contents, this awk solution can be adapted quite easily.

BashFAQ/079 (last edited 2023-01-26 22:54:33 by emanuele6)