[net.sources] Some gripes about WARP

mek@pyuxss.UUCP (08/30/83)

Warp Gripes:
Well, after about a week of getting warp to work and trying to
find the display bug, I decided I'd rather go back to having lunch during
my lunch hour.

WARP is irritating to play; it just plain doesn't handle the
screen properly: for instance, the beginning code causes the variable "DO"
to be set to the cursor down character, which on most terminals gets defined
as NL. This may be part of the confusion that results in the enterprise
or base ending up in the left margin whenever you type a 'J'. I tried
using the keypad down arrow character ("kd"), which seemed to work better,
but is not terminal independent. Further, there are some interesting
anomalies - for instance, if I try to move the enterprise into the base,
I sometimes get a bunch of B's and E's in the left side of the screen.
The opposition does "multiply" because the screen handler doesn't always
seem to clean out their characters (K, A, <, R) when they move.
I even tried to use the simple hp-1 terminal type, but that was no
major improvement.
All told, a great idea, but too bad it doesn't work.  Nice try.

crl@CSvax:Pucc-H:pur-phy.UUCP (08/30/83)

Warp works fine on a 2.8 bsd PDP-11/44 system.  It took about 1 hr. to
bring it up.  The only problems related to the fact that ints and longs
are different sizes on VAXen and 11's

Charles LaBrec
pur-ee!Physics:crl
purdue!Physics:crl

chris@umcp-cs.UUCP (08/31/83)

The two bug descriptions I just read makes me think that someone's
version of warp isn't turning of CR/LF mapping.  Either that, or your
termcap hasn't defined do= when it should have.  You *MUST* define
a down string if newline doesn't move the cursor down *without
changing the column!*  I've seen a few termcaps that were just plain
wrong about that.

(Of course, the worst thing I've ever seen is the "destructive CR"
on some terminals.  Termcap has no standard that says "\r doesn't
just \r" (it does have a "newline glitch" spec, but no "return
glitch" spec).)

Termcap is neat, but why doesn't anyone understand it?  (including
me sometimes)
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci
UUCP:	{seismo,allegra,brl-bmd}!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris.umcp-cs@UDel-Relay

alb@alice.UUCP (08/31/83)

PLEASE PLEASE PLEASE, people!  net.sources is NOT for discussions
about ANYTHING, even sources that were posted here!  If you want
to gripe or talk about warp, do it in net.games, where it belongs!

newman@utcsrgv.UUCP (Ken Newman) (09/01/83)

I think it is unfair to criticize warp because of problems
with funny termcaps. We use warp on a number of standard
terminals (Datamedias, Sorocs, VT100s) under 4.1bsd and have
no display problems whatsoever (or rand # problems). Maybe
somebody should start hacking on the termcaps for these
nuclear-powered hp terminals. (Or maybe it's the non-bsd
system differences). Warp was done in a certain environment
and runs very well in that environment. Just because it
doesn't run on all terminals in any environment doesn't
justify saying "nice try but it doesn't work".

rcj@burl.UUCP (R. Curtis Jackson) (09/22/83)

I had the same problem.  If you are talking about the new fixes that
were posted (the ADD-ONS to warp 6.0), then I agree; trash them.  But
if you are talking about the original release of 6.0, make sure that
you compiled it with Mcc and your problems will go away.
-- 

The MAD Programmer -- 919-228-3814 (Cornet 291)
alias: Curtis Jackson	...![ floyd sb1 mhuxv ]!burl!rcj