From 94720bc7aaff353496e3d976a89426b17ddcc9ce Mon Sep 17 00:00:00 2001 From: =?utf8?q?Kai=20Gro=C3=9Fjohann?= Date: Wed, 28 May 2003 08:56:29 +0000 Subject: [PATCH] (Init Rebinding): Xref Non-ASCII Rebinding, for non-English letters. Explain how to set coding systems correctly and how to include the right coding cookie in the file. --- man/ChangeLog | 6 ++++++ man/custom.texi | 36 ++++++++++++++++++++++++++++++++++++ 2 files changed, 42 insertions(+) diff --git a/man/ChangeLog b/man/ChangeLog index ac0c0d9f88c..1f52a603228 100644 --- a/man/ChangeLog +++ b/man/ChangeLog @@ -1,3 +1,9 @@ +2003-05-28 Kai Gro,A_(Bjohann + + * custom.texi (Init Rebinding): Xref Non-ASCII Rebinding, for + non-English letters. Explain how to set coding systems correctly + and how to include the right coding cookie in the file. + 2003-05-24 Kai Gro,A_(Bjohann * trampver.texi: Version 2.0.34 released. diff --git a/man/custom.texi b/man/custom.texi index a37e5246689..98a42b33891 100644 --- a/man/custom.texi +++ b/man/custom.texi @@ -1712,6 +1712,42 @@ As you see, you represent a multi-character key sequence with a vector by listing each of the characters within the square brackets that delimit the vector. + Language and encoding settings can be a reason for failing key +binding. For instance, say you have put the following in your init +file: + +@example +(global-set-key [?\M-ö] 'shell) +@end example + +@noindent +Now it can happen that the ö character read from the keyboard is +actually different from the ö character read from your init file, even +though they look the same. In this case, Emacs will not do what you +intended. First you should check whether they are the same or +different. In the above example, you would position point (the cursor) +on the ö character and hit @kbd{C-u C-x =} (the @kbd{C-u} part is +important). The second line of the output will contain the charset. +Now hit the ö key and position point on the character thus produced. +Again, hit @kbd{C-u C-x =}. If the two charsets are different, then you +have found the problem. The solution involves putting a `coding cookie' +in your init file, @pxref{File Variables}. For example, suppose that +the ö character from the init file has charset latin-iso8859-1 whereas +the ö character from the keyboard has charset latin-iso8859-15. The +solution is to put a coding cookie into the first line of the +@file{.emacs} file, as follows: + +@example +;; -*- coding: iso8859-15; -*- +@end example + +@noindent +@xref{Non-ASCII Rebinding}, if the charset printed by @kbd{C-u C-x =} is +`eight-bit-graphic'. + + If the variable @code{keyboard-coding-system} is nil, it is probably +best to set it to the right value, according to the locale you work in. + @node Function Keys @subsection Rebinding Function Keys -- 2.39.2