home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.editors:3046 comp.mail.elm:3744
- Newsgroups: comp.editors,comp.mail.elm
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cs.utexas.edu!natinst.com!balkan!ccird!felixg
- From: felixg@coop.com (Felix Gallo)
- Subject: Re: Pico port for SysVr3
- Organization: Cooperative Computing, Inc.
- Date: Tue, 15 Dec 1992 15:06:38 GMT
- Message-ID: <1992Dec15.150638.243@coop.com>
- Followup-To: comp.editors,comp.mail.elm
- References: <MAO97I@odb.rhein-main.de> <1992Dec15.005623.23519@gremlin.muug.mb.ca>
- Sender: felixg@coop.com (Felix S. Gallo)
- Lines: 29
-
- ca> charles@gremlin.muug.mb.ca (Charles) writes:
- >oli@odb.rhein-main.de (Oliver Boehmer) writes:
- >
- >>Has anyone ported pico (pine's editor) to SysV r3?
- >>I'd be thankful to hear about it
- >
- >I've had Pico 1.6 working on ISC 3.2 2.2.1 for quite a while now (I'm
- >using it right now to type this).
- >Don't remember what I did to get it going, but I remember it
- >required a bit of hacking relating to terminal stuff.
-
- I've had whichever pico is supplied with the latest pine working
- for some time, as well. The port is fairly straightforward,
- especially with the contributed sysvr3 partial port supplied at
- cac.washington.edu. Mostly, one needs to delete all the window
- resizing code and define some unknown constants.
-
- I'm having trouble getting pine to compile and function cleanly
- under SCO 3.2.[2,4], though. I've got it to compile with only
- a few errors, but the resultant executable is...somewhat
- malfunctional.
-
- If anyone else is trying to deal with pine itself under sysvr3,
- and has either accomplished anything or wants to get it working,
- I'd appreciate contacts. I might set up a mailing list if there's
- sufficient interest.
-
- Felix Gallo
- Systems Analyst, Cooperative Computing Inc.
-