[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#2313: xterm keymapping problems suspected

Bill Mitchell writes:
> It looks to me as if the /usr/lib/kbd/keytables/*.map files should have:
>   keycode 14 = Backspace             Backspace
>   keycode 111 = Delete
> And that "stty erase ^H" should be set up by default.  Those changes
> make the linux VC operate pretty much as I'd expect, and pretty much
> as MSDOS users might expect  Where it operates not as I expect is with

I don't agree. Historically the ^? is the Unix BackSpace, ^H has just been
taken over from DOS. Why do we have to do it in a way a DOS user would
expect. IMO we should do it in a way a Unix user would expect. In fact I
don't think a DOS user worries about the codes produced but only about the
result. A BackSpace keypress should delete the character to the left while a
Delete press should delete the actual character.

> The xterm terminfo issue currently involves ncurses, since ncurses
> provides the xterm terminfo file(s).  Perhaps xbase should provide these
> files, so as to reduce the need to coordinate this between two maintainers.

You got a point here. I use ^? as BackSpace on my console and everything
works fine. However, when I start X I get some problems, despite X using the
same character for BackSpace (keycode 22 = BackSpace). The reason is that my
.login call tset which sets erase to ^? on the console, but to ^H under X. I
wonder why this happens. Is there any reason to set erase to ^H if
TERM=xterm? Once I changed that everything works fine.

Also, where's the problem allowing the delete key to return ESC [3~?


Michael Meskes 
Lehrstuhl fuer angewandte Mathematik insb. Informatik
RWTH-Aachen, D-52056 Aachen, Germany
email: meskes@informatik.rwth-aachen.de

Reply to: