Re: What is with ctrl-K on my //c??

[dalloff@freenet.columbus.oh.us (Dave Althoff)]

Return of Funky Perfesser (peteyboy@eskimo.com) wrote:
: I just borrowed a copy of Apple Access II from a friend so I could download
: binscii and shrinkit, then a comm program like zlink or something.  I was
: trying to edit the files when I noticed that while all the other keys seem
: to work ok, ctl-k didn't work properly in either pico (the editor with pine)
: or Joe's E editor. Is there something goofy about Apple's ctrl-k mapping or
: something? ctl-c, ctl-p, ctl-n, they all worked fine.

Time for a quick lesson in keyboard mapping:
TAB:  Ctrl-I
Open-Apple:  Paddle Button 0
Solid-Apple:  Paddle Button 1
Left Arrow:  Ctrl-H
Right Arrow:  Ctrl-U
Up Arrow:  Ctrl-K
Down Arrow:  Ctrl-J
Return:  Ctrl-M
Delete:  ASCII 127/255
ESC:  ASCII 27
Reset:  Hardware interrupt

Maybe you've already spotted the problem.  If you are using PICO on an
ANSI-based terminal, you are running into keyboard mapping problems,
because on a VT-100 keyboard, keys are mapped as something like:
Up Arrow:  Esc-[-A
Down Arrow:  Esc-[-B
Right Arrow:  Esc-[-C
Left Arrow:  Esc-[-D

The problem isn't with the Apples, it's with the VT-100 standard...I say
that because Apple follows the same convention as IBM, CBM, Atari, Tandy,
etc...just about all of the microcomputer folks.  It's those terminal
d00dz at DEC who decided to use strange codes.  Anyway, what's probably
happening is that the terminal program you are using is re-mapping the ^H,
^U, ^J, and ^K keys to follow the VT-100 convention.  On the Apple
keyboards, (except possibly the GS) there is no way for the computer to
detect whether you have typed the arrow key or the equivalent control-key
sequence.  So when you type ^K, the terminal program sees the ASCII code
for up-arrow, and sends the VT-100 up-cursor mapping.

As for defeating this routine, some of the terminal programs will send the
standard keypress if you hold down one of the Apple keys...i.e. OA-CTRL-K
or OA-UP.ARROW.  But this is not standard...i.e. you may need to use the
Solid Apple key, or you may find that your term program doesn't support
the feature.

I realize this is a fairly involved explanation, but I hope it helps.  I
was having enough troubles with the Kermit mapping I ended up (for now)
going back to using the Lisa as a terminal...

--Dave Althoff, Jr.
-- 
    /-\                          /\
   /XXX\       X      X          X \
  /XXXXX\     XXX    XX\X       X   <**>   (hard hat area...       )
_/XXXXXXX\__/XXXXX  XXXXXXXX   XX   o==o   (.sig under construction)