On Fri, 30 Mar 2001, Scott C. Best wrote:
Am having trouble with normal grep options in
eigerstein 2.2.16. Anyone else seen this? Getting error
messages like "sed: can't read foo..." for simple
things like:
grep -v foo /etc/passwd
Huh? sed with greap? Any thoughts on
Pi:
Woof!
That's terribly annoying.
So...forgive my non-sed'ness, but what would be the
equiv of, say: "grep -v -i FOO /etc/passwd" ?
Thanks again
-Scott, thinking about grep.lrp...
On Fri, 30 Mar 2001, Pim van Riezen wrote:
On Fri, 30 Mar 2001, Scott C.
On Fri, 30 Mar 2001, Scott C. Best wrote:
Pi:
Woof!
That's terribly annoying.
I agree, it just always seemed to annoy me personally at times where
taking a better look at it was not an option.
So...forgive my non-sed'ness, but what would be the
equiv of, say: "grep -v -i
"Scott C. Best" wrote:
[...] what would be the
equiv of, say: "grep -v -i FOO /etc/passwd" ?
sed '/[Ff][Oo][Oo]/d' /etc/passwd
Pi said:
grep -v didn't even work in the old LRP2.9.8 release. Always had to hack
around it by using sed -e "s/foo//" instead of grep -v "foo".
Busybox 0.50
Pim van Riezen wrote:
The "-i" I'm not sure about, I tend to not use regexpes all that oftenly
either.
-i is case-insensitivity.
Being a regular vi nut, I use regexps all the time. It's gotten so
bad I'm constantly having to check which regexps are allowed by which
utility (vi, sed, grep
Am having trouble with normal grep options in
eigerstein 2.2.16. Anyone else seen this? Getting error
messages like "sed: can't read foo..." for simple
things like:
grep -v foo /etc/passwd
Huh? sed with greap? Any thoughts on this? TIA!
-Scott
