🚀 go-pugleaf

I've just downloaded Procomm 2.4, and was happy to see that BS/DEL swap is now
supported.  However, Procomm still has at least one minor bug in its vt100
emulation:  when a character is printed in column 80, Procomm advances the
cursor to column 1 of the next line.  True vt100s just internally note that the
cursor should be there, but leave it in column 80.  If another character comes
in, it is printed _as if_ the cursor had been advanced to column 1, provided
the vt100 itself is set to do line wraps.  This allows vi to work regardless
of the am (automatic margin) setting in the termcap...

Also, when is Procomm going to allow the keypad to be used as a keypad?  I've
seen at least one emulator (PC/InterComm by Mark of the Unicorn) which handles
this correctly:  the keypad behaves as a cursor pad unless NumLock is on; in
NumLock mode it behaves as the vt100 keypad.  Of course a couple things still
get moved around, but it's pretty intuitive.  And PC/InterComm leaves F5-F8
behaving as cursor keys always, for those who need to alternate between the
arrow keys and the numeric keypad often.  My problem with the Procomm way
of mapping the keypad is that it is backwards.  It attempts to map the function
keys into a layout physically similar to the vt100 keypad.  However, when I
need to use the keypad, I am familiar with the key names, not their position.
I know for instance that I want PF1 7 for the Command: prompt in EDT.  Procomm
then forces me to figure out that the 7 is in row 2 column 1, which would map
to PF3 (right?).  Anyway, it's tough to use...

Does someone know if the DataStorm people are on the net?  I'd like to send
them these suggestions, unless of course they already read this group!

			-Colin Kelley ..{cbmvax,pyrnj,psuvax1}!vu-vlsi!colin