Re: Bug#2313: xterm keymapping problems suspected
Raul Miller writes:
> My current preference is to track the defaults as closely as possible,
> but to give people a clear option for something more msdos-like. By
> the way, here's what stty says about a linux session [which does not
> appear to have been configured by any prior stty's]:
> intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
> eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W;
At first I thought this wasn't be correct in an xterm as I always get rase =
^H. However, I found out that this behaviour wasn't the default but caused
by tset. So if I get this right this is a bug in tset, correct?
BTW stty sane sets erase to ^? as does tset on the console. Chnaging tset
for xterm could be a way to find an end in this discussion.
Lehrstuhl fuer angewandte Mathematik insb. Informatik
RWTH-Aachen, D-52056 Aachen, Germany