Path: utzoo!attcan!uunet!husc6!rutgers!ucsd!ucbvax!MTUS5.BITNET!HEINEKEN
From: HEINEKEN@MTUS5.BITNET
Newsgroups: comp.sys.apple
Subject: BITNET mail follows
Message-ID: <8808080851.aa11296@SMOKE.BRL.MIL>
Date: 8 Aug 88 13:50:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 35

Date: 8 August 88, 08:38:50 EST
From: Steve King                                     HEINEKEN at MTUS5
To:   INFO-APPLE at BRL.MIL

> However, ATP has this annoying little problem of requiring the
> solid-apple key to be depressed for the arrows to work properly in
> emulation mode.  I have tried to compensate for this problem by
> defining macros for the arrow keys.  (ie. ^[[A, ^[[B, etc.)
> This scheme /seems/ to work without any problems on my VMS account,
> but it gives me problems in Unix.  For example, when I run
> Visual News and depress the arrow key, it gives me two erros
> that say undefined key.  Why should this be?  Of course, this problem
> is easily corrected by depressing the closed-apple key, but that is
> very annoying and requires who hands to do it.  Are there any
> problems that might arise from defining the ansi sequences as macros,
> or is there anyting special that unix requires to work with vt100
> emulators?
> Gregory A. Tucker

Using macros for cursor keys shouldn't be an intrinsic problem.  Whenever
you depress a key, ATP grabs it, checks its macro table to see if you've got
a macro set up for that key, and initiates the proper series of keystrokes
(meaning, it either sends your macro or just passes on the key you pressed.)
This is all it does with the CA-Arrow combinations to give cursor control
under VT100, unless I miss my guess.  You say that your macros work under
VMS, but not Unix.  ATP's predefined CA-Arrow combinations always work...
Hmmm...  I'd say you didn't define your macros *quite* right.  It looks like
your VMS machine is more forgiving than your Unix machine in the way it
handles keystrokes.  I don't know the VT100 cursor commands myself, but I'd
guess you need to alter your macros slightly to get the Unix machine to accept
them.  After all, the "built-in" CA-Arrow "macros" work fine...  Just find
out *EXACTLY* what codes they're sending and emulate them.

                                               --Steve King
                                                 HEINEKEN @ MTUS5.bitnet