iraf.net

Hello Doug, I'm not sure what the problem could be. You are running gterm on the
Sun 386i and then rlogin to a Sun-4 to run IRAF. This shouldn't present any
special problems. (The control sequences returned by the arrow keys on the
386 are different from Sun-4 arrow keys, but this is irrelevant in cursor
mode.) Give me a sample command sequence; I'll try to repeat it here.Suzanne

Doug, I may have misunderstood your previous mail. In cursor mode, the
arrow keys are disabled. If you move the mouse to another window and
try to use the arrow keys, they won't behave as expected until the
active cursor read in the gterm graphics window is terminated. Does
that have any bearing on the problem? Are you seeing this behavior with
arrow keys or all keys?

Sorry to be so dense, but I have yet to grasp the problem. What window
are you in when you type the character and get the keycodes? A gterm text
window, gterm graphics window or some other sort of window? Is a cursor read
in progress in the gterm graphics window at the time? By that I mean, is the
crosshair cursor showing in the gterm graphics window? When you type the
single character 'A' in the window, is the three character keycode '101'
echoed?Thanks for your patience... this is like nothing I've seen before!Suzanne

Interesting... in your testing, you should log the terminal i/o with stty: cl> stty logio
cl> do something to get the garbage characters
cl> stty clearYou'll then have a file named home$ttyio.log that contains all terminal
input and output. Mail it to me if you like. Sounds like the cursor
report returned after an RC is garbled. Could the GIN terminator have
been reset somehow? I assume this only happens when using the 386 as a
smart terminal for a remote IRAF session; it is never seen when running
IRAF directly on the 386.Suzanne