Path: utzoo!mnetor!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!mailrus!umix!umich!mibte!gamma!ulysses!thumper!faline!bellcore!rutgers!mtunx!lzaz!lznv!psc
From: psc@lznv.ATT.COM (Paul S. R. Chisholm)
Newsgroups: comp.sys.ibm.pc
Subject: Re: MKS vi bug
Message-ID: <1354@lznv.ATT.COM>
Date: 6 Apr 88 15:19:37 GMT
References: <3706@killer.UUCP> <5060020@hpccc.HP.COM>
Organization: AT&T
Lines: 23
Summary: yep; more details follow

< If you lined all the news readers up end-to-end, they'd be easier to shoot. >

In article <5060020@hpccc.HP.COM>, lufkin@hpccc.HP.COM (Paul Lufkin) writes:
> I'm having trouble manipulating strings containing the pipe ( "|" ) 
> with MKS regular expressions in vi/ex and sed.
> 
> In other implementations of UN*X ex, the command    1,$s/||/:/g
> would change all occurences of "||" to ":".
> 
> In MKS vi I get the error message 'Badly constructed regular expression'.
> Escaping the |'s does not help (ie. /\|\|/ ), nor does setting 'nomagic'.
> 
> Paul Lufkin, Jr., Hewlett-Packard Application Support Division
> lufkin@hpccc or [hpda|hpfcla]!hpwcso!paul, (415) 691-5780

I'll be dipped; you're right.  Searching for || works just fine.  Weirder
than that, after you've searched for ||, using that as the previous
regular expression, you *can* change it; that is, :s//:/g<ret> works
just fine.  Gee, I think I'll send these guys some E-mail.

-Paul S. R. Chisholm, {ihnp4,cbosgd,allegra,rutgers}!mtune!lznv!psc
AT&T Mail !psrchisholm, Internet psc@lznv.att.com
I'm not speaking for my employer, I'm just speaking my mind.