home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #16 / NN_1992_16.iso / spool / comp / unix / shell / 3104 < prev    next >
Encoding:
Internet Message Format  |  1992-07-23  |  910 b 
  1. Xref: sparky comp.unix.shell:3104 comp.unix.questions:9348
  2. Newsgroups: comp.unix.shell,comp.unix.questions
  3. Path: sparky!uunet!mcsun!sunic!aun.uninett.no!ugle.unit.no!news
  4. From: Harald.Eikrem@delab.sintef.no
  5. Subject: Re: What's wrong with this sed command?
  6. In-Reply-To: Harald.Eikrem@delab.sintef.no's message of 23 Jul 92 19:22:52
  7. Message-ID: <1992Jul23.194512*Harald.Eikrem@delab.sintef.no>
  8. Sender: news@ugle.unit.no (NetNews Administrator)
  9. Organization: SINTEF DELAB, Trondheim, Norway.
  10. References: <MONTNARO.92Jul21160321@ausable.crd.ge.com> <glaze.2520@glaze>
  11.     <1992Jul23.090023.17661@physiol.su.OZ.AU>
  12.     <1992Jul23.192253*Harald.Eikrem@delab.sintef.no>
  13. Date: 23 Jul 92 19:45:12
  14. Lines: 6
  15.  
  16. I just sed....:)
  17. ! !     sed 's?: (\./)*?: ?'        WRONG WRONG WRONG
  18. ! 
  19. ! You can do that with GNU sed.  One more reason for everybody to rm /bin/sed
  20.  
  21. Not to mislead anybody, the egrep (...) still becomes \(...\) in GNU sed.
  22.