Article-I.D.: ece-csc.3131
Posted: Sat Nov 29 13:33:47 1986
Date-Received: Sun, 30-Nov-86 19:34:34 EST
Organization: the Vulcan Institute of Technology, Dept. of Science Fiction
Lines: 35
Summary: function/cursor keys don't work

Engineering.
I have been using Dave Wecker's VT100 program (v2.3, 861101), and have 
found that the function keys (including arrows) do not seem to work reliably.

If I hit the cursor keys SLOWLY (ie, maybe wait a second between successive
keystrokes), things usually work ok.  However, if I hit the keys a little
bit more rapidly, or just hold one down, VT100 invariably gets sick
and splatters lots of garbage out.  Usually this garbage consists of a 
a single character repeated over and over -- usually I'll get the letter
"U" printed many times.  Usually after it spits out enough characters
it stops and things work again (as long as I don't use the arrow keys).
Sometimes it just spits out the character seemingly forever; other times
the system freezes and I have to exit the program (that hasn't happened
many times though and I can't remember if VT100 still exited neatly via
the close gadget or whether it required a reboot to kill the process).
This same behavior is shown by the other function keys.

The compiler doesn't seem to be at fault this time -- both Lattice 3.03B and
Manx versions of the program do the same thing.


Does anybody know what the problem might be?

Also:  some people have complained about the visible beep option not working.
       That DOES work just fine in my version (I edited vt100.h to set
       default beep volume to zero).
 
Oh yes -- I *did* edit vt100.h to make sure the #define LATTICE and
          #define MANX were set appropriately for the compiler being used.

Other than for this one problem, the program seems to work really well;
overall I am extremely pleased with it.  I just wish I could use my
functions keys with my editor!

   -- Mark Lanzo --

Article-I.D.: pttesac.341
Posted: Sun Nov 30 22:30:48 1986
Date-Received: Mon, 1-Dec-86 02:54:21 EST
References: <3131@ece-csc.UUCP>
Reply-To: vanam@pttesac.UUCP (Marnix van Ammers)
Organization: Pacific*Bell ESAC, San Francisco
Lines: 23

In article <3131@ece-csc.UUCP> mark@ece-csc.UUCP (Mark Lanzo) writes:
 > Engineering.
 > I have been using Dave Wecker's VT100 program (v2.3, 861101), and have 
 > found that the function keys (including arrows) do not seem to work reliably.

I just checked and my VT100 V2.3 does not have this problem.  I just
used vi to look through a file and I could type any of the arrow
keys (didn't test the function keys) as fast as I wanted.  I could also
hold them down so they'd repeat.  All worked just fine.

I compiled with manx.

I have hit a different problem/bug twice though.  Once using version 2.2
and once now with version 2.3 .  And that is that all of a sudden I find
that my period (.) key is acting like a break key.  Typing the right
Amiga key doesn't clear the problem.  When this happened I could not
find a way to clear the problem short of rebooting the whole system.

Marnix
-- 
Marnix A.  van\ Ammers		Work: (415) 545-8334
Home: (707) 644-9781		CEO: MAVANAMMERS:UNIX
{ihnp4|ptsfa}!pttesac!vanam	CIS: 70027,70

Article-I.D.: ut-sally.6478
Posted: Mon Dec  1 15:54:12 1986
Date-Received: Mon, 1-Dec-86 21:18:25 EST
References: <3131@ece-csc.UUCP> <341@pttesac.UUCP>
Organization: U. Texas CS Dept., Austin, Texas
Lines: 22
Summary: Arrow keys, strange lines

In article <341@pttesac.UUCP> vanam@pttesac.UUCP (Marnix van Ammers) writes:
 > In article <3131@ece-csc.UUCP> mark@ece-csc.UUCP (Mark Lanzo) writes:
 >>Engineering.
 >>I have been using Dave Wecker's VT100 program (v2.3, 861101), and have 
 >>found that the function keys (including arrows) do not seem to work reliably.
 > 
 > I just checked and my VT100 V2.3 does not have this problem.  I just
 > used vi to look through a file and I could type any of the arrow
 > keys (didn't test the function keys) as fast as I wanted.  I could also
 > hold them down so they'd repeat.  All worked just fine.
 > 
 > I compiled with manx.
 > 
 > Marnix
---------------------
I compiled with Lattice (version ?.??). If I keep pressing any of the arrow 
keys in vi, a lot of lines with just one character (usually "C") get inserted 
in the in the file.

-srinivas

srinivas@sally.utexas.edu

Article-I.D.: husc2.1047
Posted: Mon Dec  1 15:16:03 1986
Date-Received: Mon, 1-Dec-86 21:23:22 EST
Organization: Harvard University Science Center
Lines: 12

In article <341@pttesac.UUCP> vanam@pttesac.UUCP (Marnix van Ammers) writes:
 > 
 > I have hit a different problem/bug twice though.  Once using version 2.2
 > and once now with version 2.3 .  And that is that all of a sudden I find
 > that my period (.) key is acting like a break key.

Me, too.  Aliasing "." to "." in my vt100.init seems to have cleared the
problem up.

			A. Wen
			wen@harvunxu.BITNET
			wen%husc4@harvard.HARVARD.EDU

Article-I.D.: jade.1789
Posted: Tue Dec  2 13:03:43 1986
Date-Received: Wed, 3-Dec-86 09:20:33 EST
References: <1047@husc2.UUCP>
Sender: usenet@jade.BERKELEY.EDU
Reply-To: chapman@eris.BERKELEY.EDU (Brent Chapman)
Organization: UNIXversity of California at Berkeley
Lines: 33

In article <1047@husc2.UUCP> wen@husc2.UUCP (wen) writes:
 > In article <341@pttesac.UUCP> vanam@pttesac.UUCP (Marnix van Ammers) writes:
 >> 
 >> I have hit a different problem/bug twice though.  Once using version 2.2
 >> and once now with version 2.3 .  And that is that all of a sudden I find
 >> that my period (.) key is acting like a break key.
 > 
 > Me, too.  Aliasing "." to "." in my vt100.init seems to have cleared the
 > problem up.

I've hit this several times.

I haven't yet taken the time to track it down (final exams are coming up
soon...), but it seems that it only happens when I invoke a new CLI using
POPCLI, and then do an 'endcli' before returning to vt100.  (Side note:
most of the time when I invoke POPCLI from within vt100, it's to format
a disk, so the FORMAT program might be part of the problem as well.)

To reset things after the '.' key wedges, I usually just have to exit and
then restart vt100.

So, lessee, we've got a bad interaction somewhere, between at least
four, and possibly five programs: VT100, POPCLI, NEWCLI, ENDCLI, and possibly
FORMAT.  Anyone want to take the time to track it down?  I'll do it when I
get around to it, but that may not be soon.


Brent

--
Brent Chapman

chapman@eris.berkeley.edu	or	ucbvax!eris!chapman

Article-I.D.: neoucom.331
Posted: Wed Dec  3 09:29:18 1986
Date-Received: Wed, 3-Dec-86 22:50:55 EST
Organization: Northeastern Ohio Universities College of Medicine
Lines: 42
Summary: garbage due to vi timeout

In article <6478@ut-sally.UUCP>, srinivas@ut-sally.UUCP (Srinivasan Sankaran) writes:
 >  ...
 >  I compiled with Lattice (version ?.??). If I keep pressing any of the arrow 
 >  keys in vi, a lot of lines with just one character (usually "C") get inserted 
 >  in the in the file.
 >  
 >  -srinivas

I sounds like you are getting bitten by the timeout in vi that
differntiates terminal generated escape sequences from the the user
pressing the escape key, then after n milliseconds typing some
command.

On the VT100, the right arrow generates ^[ [ C, and in the keypad
mode generates ^[ O c, which means that if things are going slow,
and vi has you in keypad mode (which it does for the "normal" vt100
termcap or terminfo) that you are going to exit from insert mode,
and then suddenly find yourself with a capital C on the line above
the one you were working on.

Here, we run over ethernet servers to the Vax and occasionally, an
arrow escape sequence gets broken up between two ethernet packets
and results in an unwanted insetion of A,B,C, or D depending on the
arrow pushed.  That's how I first encountered this on a real
vt100.

I'm not a vi expert; perhaps, you could change the durration of the
timeout, or else operate at a lower baud rate, as the timeouts are
calculated proportional to the baud rate.

You also might try recompiling under Aztec rather than Lattice, as
the stdio functions are faster in Lattice, so I'm told.  I have a
version of DBW's vt100 version 2.3 that was compiled under Lattice
that our vax seems to believe is a real vt100 without problems.

BTW:  thanks DBW.  vt100 is really nice, especially the kermit.

Bill Mayhew
Division of Basic Medical Sciences
Northeastern Ohio Universities' College of Medicine
Rootstown, OH  44272  USA    phone:  216-325-2511
(...!cbatt!neoucom!wtm    wtm@neoucom.UUCP)

Article-I.D.: neoucom.332
Posted: Wed Dec  3 09:34:42 1986
Date-Received: Wed, 3-Dec-86 22:51:52 EST
References: <3131@ece-csc.UUCP> <341@pttesac.UUCP> <6478@ut-sally.UUCP>
Organization: Northeastern Ohio Universities College of Medicine
Lines: 11
Summary: Oops, Correction!!


Hold it!  Before you mail me that nastly letter, what I meant to
say in that last article was "Maybe you should try to recompile
using Aztec C rather than Lattice, as the stdio functions are
faster than in Lattice, so I've been told"

What I said was accidentally turned around!  Chalk it up to not
having enough cups of coffee yet this morning!  Sorry if I raised
anybody's blood pressure!

--Bill

Article-I.D.: gtss.158
Posted: Thu Dec  4 13:31:04 1986
Date-Received: Fri, 5-Dec-86 06:35:50 EST
References: <3131@ece-csc.UUCP> <341@pttesac.UUCP> <6478@ut-sally.UUCP>
Reply-To: chas@gtss.UUCP (Charles Cleveland)
Organization: Georgia Tech Surface Studies
Lines: 20

In article <6478@ut-sally.UUCP> srinivas@ut-sally.UUCP (Srinivasan Sankaran) writes:
 > I compiled with Lattice (version ?.??). If I keep pressing any of the arrow 
 > keys in vi, a lot of lines with just one character (usually "C") get inserted 
 > in the in the file.

I think your bug (that's the right arrow key you usually hit, right?) is due to
the lack of a normal/application mode for the cursor keys which is independent
of the normal/application mode for the keypad.  Wecker sets application cursor
keys whenever application keypad keys are set.  As I mentioned in another
posting, which only went out today due to hardware problems, I fixed this and
will post diffs if enough interest is displayed in it.


-- 
Charles Cleveland			chas@ss.physics.gatech.edu
Georgia Tech School of Physics
Atlanta, GA 30332			Georgia Tech Surface Studies

...!{akgua,allegra,amd,hplabs,ihnp4,masscomp,ut-ngp,rlgvax,sb1,
	uf-cgrl,unmvax,ut-sally}!gatech!gtss!chas

Article-I.D.: videovax.4090
Posted: Sun Dec  7 04:02:57 1986
Date-Received: Mon, 8-Dec-86 05:08:17 EST
References: <3131@ece-csc.UUCP> <341@pttesac.UUCP> <6478@ut-sally.UUCP> <158@gtss.UUCP>
Reply-To: stever@videovax.Tek.COM (Steven E. Rice, P.E.)
Organization: Tektronix Television Systems, Beaverton, Oregon
Lines: 18
Summary: Mail the diffs, post the diffs, but send 'em!

In article <158@gtss.UUCP>, Charles Cleveland (chas@gtss.UUCP) writes:

[ quotes description of arrow key bug ]

 >  I think your bug (that's the right arrow key you usually hit, right?) is
 >  due to the lack of a normal/application mode for the cursor keys which
 >  is independent of the normal/application mode for the keypad.  Wecker
 >  sets application cursor keys whenever application keypad keys are set.
 >  As I mentioned in another posting, which only went out today due to
 >  hardware problems, I fixed this and will post diffs if enough interest
 >  is displayed in it. 

Mail the diffs!  Post the diffs!  But please, send 'em!!

					Steve Rice

----------------------------------------------------------------------------
{decvax | hplabs | ihnp4 | uw-beaver}!tektronix!videovax!stever