Re: umlauts (8bit characters) input

[Hendrik Sattler]

David Kastrup wrote:

> Hendrik Sattler <sattler2000@gmx.de> writes:
> 
>> Peter Dyballa wrote:
>>> Are you running Emacs freely as an X11 client or is it
>>> no-windows inside a terminal emulation? In the second case you're a bit
>>> dependant of what the terminal emulation is doing. It might convert
>>> 8bit to 7bit.
>>
>> Yes, it is a no-windows instance inside KDE's konsole because the X emacs
>> interface is just sooo ugly. Konsole does not strip of the 8th bit, as
>> EVERYTHING els is working just fine (bash, mcedit, even VI!). The
>> absolutly only exception is emacs.
>> And yes, if I change my locale to UTF-8, emacs shall just follow case
>> without me having to edit the whole .emacs file again.
> 
> And Emacs does just that.  Throw out whatever customization of locales
> and whatsoever you have in your .emacs, or start with an empty .emacs,
> and it should work.

Thanks, that was the right hint :)
I made a "rm -rf .emacs*" in my home dir and started emacs, still no
umlauts. However, you say it works with that so I went to a VT and started
emacs there: works.
Then I started a minimal X "startx /usr/bin/X11/xterm -- :1" and it does not
work, there. Hmm, must be some X thing, then.

I looked at all environment variables: lots of differences but the main
thing: TERM=linux works, TERM=xterm does not work.

That make me look for why this is like that and I straced emacs to find
open("/usr/share/emacs/21.3/lisp/term/xterm.el", O_RDONLY|O_LARGEFILE) = 3
Hey, that's just so easy:
/usr/share/emacs/21.3/lisp/term# mv xterm.el xterm.el.old
/usr/share/emacs/21.3/lisp/term# cp linux.el xterm.el

And yes, works now. The main difference is that xterm.el adds:
(define-key function-key-map "\e[A" [up])
(define-key function-key-map "\e[B" [down])
(define-key function-key-map "\e[C" [right])
(define-key function-key-map "\e[D" [left])
(define-key function-key-map "\e[2~" [insert])
(define-key function-key-map "\e[4~" [select])
(define-key function-key-map "\e[5~" [prior])
(define-key function-key-map "\e[6~" [next])
(define-key function-key-map "\e[11~" [f1])
(define-key function-key-map "\e[12~" [f2])
(define-key function-key-map "\e[13~" [f3])
(define-key function-key-map "\e[14~" [f4])
(define-key function-key-map "\e[15~" [f5])
(define-key function-key-map "\e[17~" [f6])
(define-key function-key-map "\e[18~" [f7])
(define-key function-key-map "\e[19~" [f8])
(define-key function-key-map "\e[20~" [f9])
(define-key function-key-map "\e[21~" [f10])
(define-key function-key-map "\e[23~" [f11])
(define-key function-key-map "\e[24~" [f12])
(define-key function-key-map "\e[29~" [print])

What do those do? I am not very familiar with escape codes but should I file
a bug report against the Debian package?
What's the bug, then: the wrong TERM env var or the above file?

HS