home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: biz.sco.opendesktop
- Path: sparky!uunet!nwnexus!Celestial.COM!bill
- From: bill@Celestial.COM (Bill Campbell)
- Subject: Re: grep bug??
- Organization: Celestial Software, Mercer Island, WA
- Date: Tue, 22 Dec 1992 16:22:28 GMT
- Message-ID: <1992Dec22.162228.11109@Celestial.COM>
- References: <m0n3nHh-0001dmC@netex.netx.com>
- Lines: 31
-
- In <m0n3nHh-0001dmC@netex.netx.com> netxcom!jwc%netex.netx.com@uunet.UU.NET (JC ) writes:
-
- :I ran across a problem with SCO ODT/Unix 1.1 grep. It seems to be confused
- :when you specify the -e option. For example,
-
- : cat file |grep -y -e "string"
-
- :results in
-
- : Usage: grep -bchilnsvy [-e expr] [-f expr_file] pattern file . . .
-
- :the -y option makes no difference. The following forms DO work:
-
- : cat file |grep -y "string"` >>> piping, no -e option
- : grep -y -e "string" file` >>> -e option, no piping
-
- I tried both variants on my UNIX 3.2v4 and Xenix 2.3.4 systems
- and they worked much to my surprise since I thought the -y option
- had been replaced with -i (IMHO one of the dumber things to
- happen to UNIX since neither makes much sense and changing it
- breaks 20 years worth of scripts :-).
-
- I replaced the SCO grep and egrep with the gnu versions several
- months ago when I ran into a bug with egrep while compiling perl.
-
- Bill
- --
- INTERNET: bill@Celestial.COM Bill Campbell; Celestial Software
- UUCP: ...!thebes!camco!bill 6641 East Mercer Way
- uunet!camco!bill Mercer Island, WA 98040; (206) 947-5591
- SPEED COSTS MONEY -- HOW FAST DO YOU WANT TO GO?
-