From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Cannot remap umlaut keys
Date: Mon, 10 Nov 2003 16:17:25 GMT [thread overview]
Message-ID: <jwvvfpsi4vl.fsf-monnier+gnu.emacs.help@vor.iro.umontreal.ca> (raw)
In-Reply-To: 87islw6jen.fsf@ID-28718.user.uni-berlin.de
>> (local-set-key [ö] "{")
> [ö] or [?ö]?
Oops, it should have been [?ö] indeed.
> I forgot to mention that I tried to use [?ö] before I posted my article.
> [?ö] (or [ö]) neither works under X *nor* on the console.
> state 0x0, keycode 47 (keysym 0xf6, odiaeresis), same_screen YES,
> XLookupString gives 1 bytes: "ö"
> I'm pretty sure that [?\366] worked in earlier versions of Emacs. I
> think that I started to use the above piece of code when Emacs 19 was
> current.
No doubt about that. But I fixed this Emacs-19 bug ;-)
>> This might not always work, tho. If it doesn't, then maybe your
>> locale is not set properly.
> The locale is set to de_DE.iso88591 which, according to "locale -a" is
> supported by the C library. I also tried to use de_DE.
Hmm... it should have worked.
> My .emacs is encoded in ASCII. I encoded it in Latin-1 when I
> experimented with [?ö]. I also tried UTF-8.
Have you tried putting a -*- coding: latin-1 -*- on the first line
to make sure that it is read with the proper coding system ?
The problem is that there are many different ö characters in Emacs
and it's important that Emacs read it as (make-char 'latin-iso8859-1 118)
(i.e. 2294) since it is the event generated by Emacs for the odiaeresis
key in an iso-8859-1 locale.
Stefan
next prev parent reply other threads:[~2003-11-10 16:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 17:08 Cannot remap umlaut keys Andreas Voegele
2003-11-07 18:21 ` Stefan Monnier
2003-11-07 19:57 ` Andreas Voegele
2003-11-10 16:17 ` Stefan Monnier [this message]
2003-11-12 8:12 ` Andreas Voegele
2003-11-12 13:53 ` Stefan Monnier
2003-11-14 13:11 ` Andreas Voegele
2003-11-14 17:23 ` Stefan Monnier
2003-11-07 21:02 ` Reiner Steib
2003-11-08 1:23 ` Andreas Voegele
2003-11-08 12:34 ` Reiner Steib
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvvfpsi4vl.fsf-monnier+gnu.emacs.help@vor.iro.umontreal.ca \
--to=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).