In egrep (grep 3.0), the order of options (multiple --include and --exclude),
is surprisingly significant.
I was puzzled by 5 extra output lines in my first egrep,
so I did another egrep, with the --include moved up front.
Known bug?
Yes, I realize that the include by itself would have been suffic
> On 10/3/20 12:00 PM, John Ruckstuhl wrote:
> > In egrep (grep 3.0), the order of options (multiple --include and
> > --exclude), is surprisingly significant.
> > I was puzzled by 5 extra output lines in my first egrep, so I did
> > another egrep, with the --include
uot; \( -true \) \
> -o \
> "$INCFIRST" \( ! -name "*.bak" -name "*.py" \) \
> \) \
> -o \
> \( ! -name "*.bak" -name "*.py" \) \
> \) |
> while read F; do egrep -i -n -l "$PA
