Subject: Editing problems in PICO

From: Joseph McWilliams <[email-masked]>
Date: Sat, 24 Aug 1996 12:18:48 -0500

Here's the scenario:

Pine_3.95 and Pico_2.9 code compiled and running in NeXTStep 3.3.  In a
console terminal window, editing in both Pine and Pico works fine.  Over a
modem, while Pine still works as advertised, Pico has enough problems to
render it worthless.

- Only a few Ctrl-codes are recognized.  Luckily Crtl-X is one of those.
The others simply pass ANSI characters to the screen, diamonds, arrows,
faces, etc.
- The keyboard characters are recognized but a <return> produces only a
carrage return but no new-line

The problem isn't with the modem.  I can dial up this machine and Pico is
broken.  If I then telnet to another machine and telnet back to the first
machine, Pico will now work fine.

Should Pico be recompiled with a different setup?

Any suggestions would be welcome.

Joe McWilliams