[comp.protocols.tcp-ip.ibmpc] NCSA Telnet 2.3beta15 & 84 keyboards

08071TCP@MSU.BITNET (Doug Nelson) (03/30/91)

>I just upgraded to the NCSA Telnet PC 2.3b15 version.  Why does this new
>version not support the old 84 key keyboards, or am I missing something?
>
>When using "vi", the cursor movement keys on the numeric keypad give me
>r, t, q, .......    With numlock on, I get numbers.
>
>This version (2.3b15) supports the 101 "extented" keyboards just fine.
>
>The older version (NCSA 2.2) worked just fine with both 84 and 101 key'ers.
>
>Me thinks that modifying the "telnet.key" file to include the correct
>KERMIT's scan codes is the solution, so I ran the "scanchec" program.  It
>reports the codes should be:
>
>set key \328    \Kuparr         ; grey up arrow for vt100 uparrow
>set key \336    \Kdnarr         ; grey down arrow for vt100 downarrow
>set key \331    \Klfarr         ; grey left arrow for vt100 leftarrow
>set key \333    \Krtarr         ; grey right arrow for vt100 rightarrow
>
>BUT, this did'nt work (I changed the 44xx codes to the 3xx codes above).
>
>This file is in the same directory as "TELBIN.EXE" and I set the pathname
>to this keyboard file in the "CONFIG.TEL" file.
>
>Any help would be great!

Well, I haven't used NCSA Telnet, but I'm familiar enough with Kermit.
This is the behavior I'd expect to see if those keys were defined with
the functions \Kkp2, \Kkp4, etc., but NOT if you succeeded in changing
them to \Kuparr, etc.  If you're sure you have changed the right files
(you are using the right environment variable name - it changed with a
recent version), then you have either found a bug in the handling of the
"\Kuparr" and related functions, or their key mapping numbers aren't
completely consistent with Kermit.  You could do one or more of the
following:

1.  Modify your Unix termcap to not use keypad application mode.

2.  Modify "telnet.key" to define these keys with the raw character
    sequences (e.g. "\27[A"), rather than the \K... functions.  It *should*
    be the keys in the 327-337 range (or maybe 839-849).

3.  Add "map" entries to your Unix .exrc file to define the key sequences
    that application mode sends as the appropriate "vi" function, as follows:

        map ^[Or j
        map ^[Ot h
        map ^[Ov l
        map ^[Ox k

    where "^[" is the escape key (you'll need to escape it with Ctrl-V when
    entering it).

Doug Nelson
Michigan State University