Q: OS X v10.7 - egrep Doesn't Work
-
by whatitdowhatitdontdowhatitizzz,Nov 20, 2011 11:45 PM
whatitdowhatitdontdowhatitizzz
Nov 20, 2011 11:45 PM
in response to whatitdowhatitdontdowhatitizzz
Level 1
(0 points)
Oops! GREP_OPTIONS=-P was set...
-
by Danny Niu. Running a instance of Niux Unix operatig system.,Sep 4, 2016 10:53 PM
Danny Niu. Running a instance of Niux Unix operatig system.
Sep 4, 2016 10:53 PM
in response to whatitdowhatitdontdowhatitizzz
Level 1
(4 points)
Why was it set? where was it set? was it set by default? what does it mean?
I'm a bit worried because I need a script of mine to work on both Solaris and OSX.
-
by BobHarris,Sep 5, 2016 3:46 AM
BobHarris
Sep 5, 2016 3:46 AM
in response to Danny Niu. Running a instance of Niux Unix operatig system.
Level 6
(19,257 points)
Mac OS XDanny Niu. Running a instance of Niux Unix operatig system. wrote:
Why was it set? where was it set? was it set by default? what does it mean?
I'm a bit worried because I need a script of mine to work on both Solaris and OSX.
This is a 5 year old thread.
If you are having problems with grep or egrep maybe you should start a new post, and describe your problem.
I can tell you that I have a lot of shell scripts that run on OS X, Solaris, AIX, and Linux. I do not typically do anything fancy with egrep, but I do use it on occasion. With Solaris I have more problems with awk.
And for some of the non-POSIX commands I end up testing $(uname) and having platform specific conditional code.