From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Hendrik Sattler Newsgroups: gmane.emacs.help Subject: Re: umlauts (8bit characters) input Date: Tue, 01 Feb 2005 14:37:41 +0100 Organization: T-Online Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Trace: sea.gmane.org 1107265332 18488 80.91.229.2 (1 Feb 2005 13:42:12 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 1 Feb 2005 13:42:12 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Feb 01 14:42:12 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1CvyIA-0000Wn-Ae for geh-help-gnu-emacs@m.gmane.org; Tue, 01 Feb 2005 14:42:06 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CvyV5-0005rn-Pm for geh-help-gnu-emacs@m.gmane.org; Tue, 01 Feb 2005 08:55:27 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!newsmm00.sul.t-online.de!t-online.de!news.t-online.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 66 Original-X-Trace: news.t-online.com 1107265061 05 17065 FIj1rj3vh6mo03+ 050201 13:37:41 Original-X-Complaints-To: usenet-abuse@t-online.de X-ID: EwD4sgZeoe3iwgIjdpEiNnsOWfTDU13sxhEnnJxDIr4PDPUsyQ0zoP User-Agent: KNode/0.8.1 Original-Xref: shelby.stanford.edu gnu.emacs.help:128303 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org X-MailScanner-To: geh-help-gnu-emacs@m.gmane.org Xref: main.gmane.org gmane.emacs.help:23811 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:23811 David Kastrup wrote: > Hendrik Sattler 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