| The problem I'm trying to solve is how to have one regexp per
| line, with an unlimited number of lines in the file.
That's precisely what fgrep's and egrep's -f option is for: reading a file to
get the text (for fgrep) or regexps (for egrep) that the program will look
for in the input. So that's why Alan suggested using egrep -f in the first
place.
My post was because "egrep -f" gives an error "regular expression too
long". The data file I included was for the convenience of anyone who
wished to reproduce the problem for themselves. My original post is
appended.
So far the most common suggestion has been to use "fgrep -f", which
doesn't allow regexp's in the file. It would be straight-forward to
write a perl script to step through the file of regexps, but I'd
prefer "egrep -f" since it appears it should do exactly what I want.
I surprised that SRvB or anyone else didn't mention that "multigram" can
do address filtering. The source for multigram is in the procmail
distribution, even though it is only compiled during an installation of
SmartList.
However, the "bad news" is that you must "Use the Source, Luke" in order
to understand multigram, since there is no other documentation on it,
except invocations of it in the rc files which are part of SmartList.
___________________________________________________________
Alan Stebbens <stebbens(_at_)sgi(_dot_)com> (415) 933-6437
Silicon Interactive Group, Silicon Graphics, Inc. (SGI)
M/S:9L991, 2011 N. Shoreline Blvd., Mountain View, CA 94043