Subject: Re: WYSE 50 terminals

From: [email-masked] (Ray Soo)
Date: Mon, 22 Mar 93 10:16:00 EST

Operating System: HP-UX B.08.00 B 9000/360 080009001925
Mailer: Elm [revision: 66.25]

> 
> >    Is this why WYSE 60 terminal emulation doesn't work with PINE
> >    either? When I use PINE I have to run another terminal emulation
> >    e.g. VT100 for it to work.
> >
> That is likely. I don't remember what kind of terminal Wyse60 is.
> What problems are you having?
> 
> --
> ::        [email-masked]        ::   o/       ::                          ::
> ::  Abalon AB, Stockholm, Sweden  ::  /@        ::          Earth.          ::
> ::        59.19 N, 17.57 E        ::  <|\  acro ::   Love it or leave it.   ::
> ::    * All disclaimers apply *   ::   |   phil ::                          ::
> 

I'm running pine 3.05 on a Sun Sparc2 (sunOS 4.1.2) and
the text on the screen is interspersed with many "OOPS" messages.

However, I seem to be able to run the news reader "nn" on the same
machine with Wyse60 term emulation with no problems. From the user's
point of view "nn" seems to have the same sort of screen painting.

--

\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\
raymond soo                                       [email-masked]
Exicom Australia Pty Ltd                          phone: 61-2-7248480
44-46 Mandarin St.                                       61-2-7248496
Villawood NSW 2163 Australia                      fax :  61-2-7248738
\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\-/-\

---

From: "Edward K. Yagi" <[email-masked]>
Date: Sun, 21 Mar 1993 16:04:49 +22305714 (HST)

> the text on the screen is interspersed with many "OOPS" messages.

Perhaps its your Termcap entry for that terminal. I am able to use Pine3.05a
at work on a true blue wyse50 fairly well. I just had to find the termcap
entry for that terminal. 

 This is the termcap that has worked for me..

TERMCAP='wv|wyse-vp|wyse|Wyse 50 in ADDS Viewpoint emulation mode with
"enhance" on:\
	:am:do=^J:if=/usr/share/lib/tabset/wyse-adds:\
	:le=^H:bs:li#24:co#80:cm=\EY%+ %+ :cd=\Ek:ce=\EK:nd=^F:\
	:up=^Z:cl=^L:ho=^A:ll=^A^Z:kl=^U:kr=^F:kd=^J:ku=^Z:kh=^A:\
	:pt:so=^N:se=^O:us=^N:ue=^O:dl=\El:al=\EM:im=\Eq:ei=\Er:dc=\EW:\
	:is=\E`\072\E`9^O\Er:rs=\E`\072\E`9^O\Er:'

 I said 'fairly' well because I am unable to use the arrow keys on the
keypad. Control-P,Control-N etc for cursor movement all work, but Id
like to have the keypad cursor keys to work also. Looking at the termcap
info above, I tried changing the control sequences for ku,kd,kr,kl to 
control-p, control-n, control-b, control-f but Pine still does not
recognise them. Any suggestions?
						edman

Edward Yagi
[email-masked]
[email-masked]
[email-masked]

---

From: Laurence Lundblade <[email-masked]>
Date: Sun, 21 Mar 1993 22:35:40 -0500 (EST)

I think some one answered this already, but just to affirm it, Pine does
have some problems running on Televideo and Wyse terminals that other
programs may not have because of limitations of these terminals. If these
terminals have an ansi or vt100 mode that could be used to avoid the
problem. 

The problem is that these terminals require a space on the screen between
shifts from from regular video to reverse and back, and Pine can't cope
with that. In principle Pine's screen painting routines could be fixed
since there is information in termcap to alert Pine to this and most of
Pine's screen do have spaces surrounding blocks of reverse video, but it's
probably a fair amount of work. 

There is a work around for this problem that's described in the technical
notes. It is to use protected mode instead of standard reverse video and
requires modification to your local termcap.  If anyone's done this please
post your termcap entry! 

LL

---

From: Laurence Lundblade <[email-masked]>
Date: Sun, 21 Mar 1993 22:45:23 -0500 (EST)

Ooops, thought I'd read all my mail when I'd posted the last one. My guess
is that this termcap entry does the protected mode trick because the "is"
field has got a lot of stuff in it. 

I think the arrow key problem with these terminals is a bit worse. I think
they send ^J ^K ^L and ^O or such for the arrow keys. These collide
directly with some of the Pine commands so the only hope is to rearrange
the Pine key bindings. Pine doesn't pay attention to the termcap ku, kd,
kr, and kl entries in the termcap, but knows about the 5 or so most common
schemes for arrow keys. This was done because experience suggested that
the termcap entries were usually not set up correctly and we wanted Pine
to work as well as possible out of the box without a lot of configuration. 

Thanks a lot for posting the termcap entry!

LL

---

From: [email-masked] (Christer Lindh)
Date: Wed, 24 Mar 93 10:04:24 +0100

>    the text on the screen is interspersed with many "OOPS" messages.
Huh?  It says "OOPS"?  Weird!  I can't seem to find the string "OOPS"
in the pine source, who generates it?

---

From: Laurence Lundblade <[email-masked]>
Date: Wed, 24 Mar 1993 07:50:16 -0500 (EST)

It's generated by the termcap library. I don't remember under exactly what
conditions. 

LL