emacs-pretest-bug
[Top][All Lists]
Advanced

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

Re: Rebinding international characters


From: Kenichi Handa
Subject: Re: Rebinding international characters
Date: Thu, 5 Aug 2004 13:47:58 +0900 (JST)
User-agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/21.3 (sparc-sun-solaris2.6) MULE/5.0 (SAKAKI)

In article <address@hidden>, Oscar Fuentes <address@hidden> writes:

> Kenichi Handa <address@hidden> writes:
>>  In article <address@hidden>, "Eli Zaretskii" <address@hidden> writes:
>>>  However, I wonder: the manual (and AFIR the FAQ as well) suggest to
>>>  use a unibyte code, as in `[241]', to bind non-ASCII keys, saying it
>>>  works in more cases.  If this is no longer true, i.e. if using the
>>>  character itself, as in `?x', is a better (or the only) way, we should
>>>  fix the docs.
>> 
>>  Yes, but I couldn't find a place where, for instance, [241]
>>  is suggested with a brief grepping.

> I can't access the manual pages on CVS, but for 21.3 the node is
> ``Non-ASCII Rebinding"

Ah!  Thank you.  I was grepping elisp infos, not emacs
infos.  That node is as below

------------------------------------------------------------
@node Non-ASCII Rebinding
@subsection address@hidden Characters on the Keyboard
@cindex rebinding address@hidden keys
@cindex address@hidden keys, binding

If your keyboard has keys that send address@hidden characters, such as
accented letters, rebinding these keys is a bit tricky.  There are two
solutions you can use.  One is to specify a keyboard coding system,
using @code{set-keyboard-coding-system} (@pxref{Specify Coding}).
Then you can bind these keys in the usual address@hidden that you
should avoid the string syntax for binding 8-bit characters, since
they will be interpreted as meta keys.  @xref{Strings of
Events,,,elisp, The Emacs Lisp Reference Manual}.}, like this:

@example
(global-set-key address@hidden 'some-function)
@end example

@noindent
Type @kbd{C-q} followed by the key you want to bind, to insert @var{char}.

Since this puts a address@hidden character in the @file{.emacs}, you should
specify the proper coding system for that file.  @xref{Init Syntax}.
Specify the same coding system for the file that you use for your
keyboard.

If you don't specify a keyboard coding system, that approach won't
work.  Instead, you need to find out the actual code that the terminal
sends.  ....
------------------------------------------------------------

I think there's no need to mention the second solution
because now a keyboard coding system should be setup
property automatically.  And, when using X Window, we now
never receive the actual code that the termninal send.

So, have have making this node as below?

------------------------------------------------------------
@node Non-ASCII Rebinding
@subsection address@hidden Characters on the Keyboard
@cindex rebinding address@hidden keys
@cindex address@hidden keys, binding

If your keyboard has keys that send address@hidden
characters, such as accented letters, rebinding these keys
must be done by using a vector like address@hidden that
you should avoid the string syntax for binding
address@hidden characters, since they will be
interpreted as meta keys.  @xref{Strings of Events,,,elisp,
The Emacs Lisp Reference Manual}.}:

@example
(global-set-key address@hidden 'some-function)
@end example

@noindent
Type @kbd{C-q} followed by the key you want to bind, to insert @var{char}.

Since this puts a address@hidden character in the
@file{.emacs}, you should specify the proper coding system
for that file.  @xref{Init Syntax}.  Specify the same coding
system for the file that you use for your keyboard.
------------------------------------------------------------

---
Ken'ichi HANDA
address@hidden





reply via email to

[Prev in Thread] Current Thread [Next in Thread]