Subject: Pine on a Convex?

From: [email-masked] (Dave Rasmussen)
Date: Wed, 3 Feb 1993 13:37:06 -0600

Has anyone configured pine for a convex? We have a C220 running
ConvexOS 10.0.3 which is sort of a bsdish thing with ansi c. I tried
using the BSD and the ult configurations and it looks pretty ugly in
error messages so far.

---

From: "Peter W. Karlson" <[email-masked]>
Date: Thu, 4 Feb 1993 17:05:03 -0500 (EST)

I know I've heard about this before but I need to ask again, is there a
problem using NCSA telnet on a Mac and trying to cancel a message using
control C??

Thanks

-pk

---

From: Mark Crispin <[email-masked]>
Date: Wed, 3 Feb 1993 13:36:44 -0800 (PST)

If the Convex has an ANSI C compiler, try the NeXT, AIX, or A32 configurations
and see if any of those get you any closer.

---

From: Pekka Kytolaakso <[email-masked]>
Date: Thu, 04 Feb 1993 10:53:04 +0200

Your message dated: Wed, 03 Feb 1993 13:37:06 CST
> using the BSD and the ult configurations and it looks pretty ugly in

I sent my convex patches to the development team and they should be in
the next pine version.

My port is available on nic.funet.fi:/pub/unix/convex/pine3.05.tar.Z. 
It's configured to work like elm (folders are in ~/Mail/, several folder
name changes). To compile it use './build bsd'. 

Pekka Kyt|laakso
---------------------------------------------------------------
[email-masked]     Centre for Scientific Computing
[email-masked]  PL 40   SF-02101 Espoo FINLAND
Phone: +358 0 4571       Telefax: + 358 0 4572302

---

From: Laurence Lundblade <[email-masked]>
Date: Thu, 4 Feb 1993 23:13:12 -0500 (EST)

The way around this problem is described in the help text off the main
menu under frequently asked questions. I've tacked it on the end here.

LL

Page 8
      5. If ^C Doesn't Work on a Mac

There's a problem with the default configuration of the Macintosh version
of NCSA telnet which prevents Control-Cs from reaching Pine.  Under the
"session menu", select "setup keys". There's you'll see an entry for ^C.
You should make sure it's blank. If it's not, ^C won't work in Pine.
This will fix it just for the current session. To make it permanent
you have to edit the configuration file. You should add a line:

        localkeys=[0,19,17]  (but use curly braces instead of [])

somewhere after the line that contains "name=default".  Also, on
VersaTerm Pro a similar problem occurs where ^C causes a break to be
sent on the modem or serial line.