Xref: utzoo comp.editors:2311 comp.unix.sysv386:3621
Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!julius.cs.uiuc.edu!rpi!uupsi!jpradley!jpr
From: jpr@jpradley.jpr.com (Jean-Pierre Radley)
Newsgroups: comp.editors,comp.unix.sysv386
Subject: Re: vi under SCO Unix
Message-ID: <1991Jan03.012626.8892@jpradley.jpr.com>
Date: 3 Jan 91 01:26:26 GMT
References: <1991Jan02.015821.4496@jpradley.jpr.com> <Message-Id@dce.ie>
Reply-To: jpr@jpradley.UUCP (Jean-Pierre Radley)
Organization: NYC Public Unix
Lines: 27

In article <Message-Id@dce.ie> em@dce.ie (Eamonn McManus) writes:
>jpr@jpr.com (Jean-Pierre Radley) writes:
>>This is a mapping which I used daily in SCO Xenix to compose replies to
>>CompuServe messages.
>>
>>map  #1  ?#: [0-9][0-9].* S[0-9][0-9]*/?Wyt N<<Ore^[pmao/post unf^[mbO
>>
>>It fails in SCO Unix.
>
>Regular expressions are severely broken in SCO Unix, at least in 3.2.0.
>Practically any expression using the closure operator (*) can be expected
>not to work.  Your simplest solution is to grab your Xenix vi binary and
>use it instead.

I could have been more specific in my first posting, sorry.

I have SCO UNIX 3.2.2

Running "what vi" shows:

/usr/bin/vi:
	 printf.c:2.2 6/5/79
	 SCO UNIX 3.2V2 OS 09 Jun 90

I did resort to porting the Xenix 'vi' to use instead.

 Jean-Pierre Radley	    NYC Public Unix	jpr@jpr.com	CIS: 72160,1341