Translating keys

Translating keys

[Elena Garrulo]

Hello,

	I'd like to translate some keys in a mode dependent way. For example, when in c-mode, the key which 
prints "ò" should print "{"; when in text-mode should print the original character. Since the 
translation should be mode dependent, keyboard-translate is not a viable option. I've tried:

(local-set-key "ò" (lambda () (interactive) (insert "{")))

but it doesn't work. It works with other keys, for example:

(local-set-key "a" (lambda () (interactive) (insert "{")))

I think I should know the code generated by the key. Is there a way?

Anyway, the "insert" function is not useful, because the generated character does not behave like 
the original one (I've electric C enabled and the { generated by "insert" is not recognized as 
electric; the original { is).

Any help?

Thanks.

Re: Translating keys

[Peter Dyballa]

Am 16.10.2005 um 21:58 schrieb Elena Garrulo:

> I'd like to translate some keys in a mode dependent way. For example, 
> when in c-mode

Have you checked c-mode-map, 'a sparse keymap used by C mode?'

--
Greetings

   Pete

"Email is a wonderful thing for people whose role in life is to be on 
top of things. But not for me; my role is to be on the bottom of 
things. What I do takes long hours of studying and uninterruptible 
concentration."   -Donald Knuth

Re: Translating keys

[Elena Garrulo]

Peter Dyballa wrote:

> Have you checked c-mode-map, 'a sparse keymap used by C mode?'

Thank you, now I have the "electric" behaviour. Still, I cannot remap
the extended ASCII "ò" character (225 octal). Neither this:

(define-key c-mode-map "ò" 'c-electric-brace)

nor this:

(define-key c-mode-map "\225" 'c-electric-brace)

work. Standard ASCII characters do work:

(define-key c-mode-map "k" 'c-electric-brace) ;; OK
(define-key c-mode-map "\153" 'c-electric-brace) ;; OK

Re: Translating keys

[Peter Dyballa]

Am 17.10.2005 um 00:07 schrieb Elena Garrulo:

> (define-key c-mode-map "ò" 'c-electric-brace)
>
> nor this:
>
> (define-key c-mode-map "\225" 'c-electric-brace)
>
> work. Standard ASCII characters do work:
>

 From where do you know it's \225? Did you check this with C-u C-x = in 
*scratch* buffer? Can you make GNU Emacs to do a read-event or 
read-string? Could be there is a simple mismatch between what you think 
is right and what the keyboard produces ...

--
Greetings

   Pete

When in doubt, use brute force.
                 -- Ken Thompson

Re: Translating keys

[Pascal Bourguignon]

Elena Garrulo <egarrulo@muchomail.com> writes:

> Hello,
>
> 	I'd like to translate some keys in a mode dependent way. For
> example, when in c-mode, the key which prints "ò" should print "{";
> when in text-mode should print the original character. Since the
> translation should be mode dependent, keyboard-translate is not a
> viable option. I've tried:
>
> (local-set-key "ò" (lambda () (interactive) (insert "{")))

If you want to translate keys why do you use local-set-key? 
Use: keyboard-translate !

Now, if what you really want is to bind a function to a key, then use
local-set-key: (local-set-key (kbd "A-o") ...)  or whatever key
combination you use to get 'ò'.

A- = Alt
C- = Control
M- = Meta
S- = Shift
s- = Super
H- = Hyper

-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
Our enemies are innovative and resourceful, and so are we. They never
stop thinking about new ways to harm our country and our people, and
neither do we. -- Georges W. Bush

Re: Translating keys

[Stefan Monnier]

> (local-set-key "ò" (lambda () (interactive) (insert "{")))
> but it doesn't work.
> I think I should know the code generated by the key. Is there a way?

There are many different ò.  And the one sent by your keyboard's key is not
always the same depending on the version of Emacs, and the one read from
your .emacs is not always the same either depending on your locale, your
Emacs settings and maybe a -*- coding -*- cookie in the file.

Try M-: (read-event) RET and then hit your ò key.  It'll return the code
Elisp receives in response to this key (e.g. 2290).  You can then bind it
with (local-set-key [2290] "{").

> Anyway, the "insert" function is not useful, because the generated character
> does not behave like the original one (I've electric C enabled and the
> { generated by "insert" is not recognized as electric; the original { is).

Try (local-set-key "ò" "{").  The "{" part is a keyboard macro which tells
Emacs to behave as if you had typed the key sequence "{" (i.e. composed of
a single key).


        Stefan

Re: Translating keys

[Mounir AITTAHAR]

> Now, if what you really want is to bind a function to a key, then use
> local-set-key: (local-set-key (kbd "A-o") ...)  or whatever key
> combination you use to get 'ò'.

Hi,

As told in another thread(1), (local-set-key (kbd "é") ...) seems not to 
work if non-ASCII characters are entered by pressing one button, their 
button. It looks like these kind of keys cannot be reached by a local or 
global binding.

I allowed myself to tell the problem in this thread cause it is a 
related subjetc and it seems you are a french user (and you may use a 
french keyboard)

Do you know this problem and how to solve it ?

-- 
Mounir AITTAHAR
(1) /Non-ASCII characters Key binding (emacs 21.4)/

Re: Translating keys

[Pascal Bourguignon]

Mounir AITTAHAR <mounir.aittahar@fri.fr> writes:

>> Now, if what you really want is to bind a function to a key, then use
>> local-set-key: (local-set-key (kbd "A-o") ...)  or whatever key
>> combination you use to get 'ò'.
>
> Hi,
>
> As told in another thread(1), (local-set-key (kbd "é") ...) seems not
> to work if non-ASCII characters are entered by pressing one button,
> their button. It looks like these kind of keys cannot be reached by a
> local or global binding.

At least in emacs-version "22.0.50.1", it works perfectly, as well for
a directly é typed on a MacOSX AZERTY, or using C-x 8 ' e


> I allowed myself to tell the problem in this thread cause it is a
> related subjetc and it seems you are a french user (and you may use a
> french keyboard)

I am, but I never use this AZERTY monstruosity.


> Do you know this problem and how to solve it ?

(local-set-key (kbd "é") (lambda()(interactive)(insert "\ngot e acute\n")))

-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
In deep sleep hear sound,
Cat vomit hairball somewhere.
Will find in morning.

Re: Translating keys

[Mounir AITTAHAR]

>>As told in another thread(1), (local-set-key (kbd "é") ...) seems not
>>to work if non-ASCII characters are entered by pressing one button,

>>Do you know this problem and how to solve it ?

> (local-set-key (kbd "é") (lambda()(interactive)(insert "\ngot e acute\n")))

Nope, this line doesn't work : when I type "é", I don't get "got e 
acute", but "é".

I've recently tried this bind on *true* console-mode emacs, it works. I 
wonder if this not a graphical libraries problem.

Notice that in emacs 20.7 (with-xlib compiled version) non-ascii key 
bindings worked.

-- 
Mounir AITTAHAR

Re: Translating keys

[Mounir AITTAHAR]

Okay, emacs -nw (with "(set-keyboard-system latin-1)" + Xterm Meta
sends escape) and emacs/X11 have the same behaviour when type "é" in a
Azerty keyboard.

So this line :
(local-set-key (kbd "é") (lambda()(interactive)(insert "e acute")))

Or this one :
(local-set-key (kbd "é") (lambda()(interactive)(insert "e acute")))

don't insert e acute. :(

Re: Translating keys

[Pascal Bourguignon]

"Mounir AITTAHAR" <downwater@free.fr> writes:

> Okay, emacs -nw (with "(set-keyboard-system latin-1)" + Xterm Meta
> sends escape) and emacs/X11 have the same behaviour when type "é" in a
> Azerty keyboard.
>
> So this line :
> (local-set-key (kbd "é") (lambda()(interactive)(insert "e acute")))
>
> Or this one :
> (local-set-key (kbd "é") (lambda()(interactive)(insert "e acute")))
>
> don't insert e acute. :(

Of course not.


I don't see the difference between the two lines:
> (local-set-key (kbd "é") (lambda()(interactive)(insert "e acute")))
> (local-set-key (kbd "é") (lambda()(interactive)(insert "e acute")))

After:

(local-set-key (kbd "é") (lambda()(interactive)(insert "e acute")))

Type: C-x C-e C-x 8 ' e

Or perhaps, if the mode you're using rebinds C-x C-e:

M-x eval-last-sexp RET C-x 8 ' e



-- 
"Debugging?  Klingons do not debug! Our software does not coddle the
weak."

Re: Translating keys

[Mounir AITTAHAR]

> I don't see the difference between the two lines:
>>(local-set-key (kbd "é") (lambda()(interactive)(insert "e acute")))
>>(local-set-key (kbd "é") (lambda()(interactive)(insert "e acute")))

Whoops :-( Don't remember my thoughts when I wrote this

> (local-set-key (kbd "é") (lambda()(interactive)(insert "e acute")))
> 
> Type: C-x C-e C-x 8 ' e

Yes, it works in that case. I suppose now that kbd translate "é" into 
C-x C-e C-x 8 (bound to "keyboard macro" iso-transl-e-acute even if rebound)

Let's continue in /Non-ASCII characters Key binding (emacs 21.4)/ 
thread, which fit more for the way of resolution I might found.


-- 
Mounir AITTAHAR

Re: Translating keys

[Stefan Monnier]

> As told in another thread(1), (local-set-key (kbd "é") ...) seems not to
> work if non-ASCII characters are entered by pressing one button, their

Check some of those threads that have been running these days.
I've recently posted an explanation of the problem along with solutions.


        Stefan

Re: Translating keys

[Mounir AITTAHAR]

> Check some of those threads that have been running these days.
> I've recently posted an explanation of the problem along with solutions.

Do you mean in "Non ascii key bindings ?" Yep, I've read. And answered :)

-- 
Mounir AITTAHAR

Re: Translating keys

[Mounir AITTAHAR]

> Check some of those threads that have been running these days.
> I've recently posted an explanation of the problem along with solutions.

My server news is really rubbish.

By Google, I've read your message (hope this is this one you told about)_:

> Try M-: (read-event) RET and then hit your ò key.  It'll return the code
> Elisp receives in response to this key (e.g. 2290).  You can then bind it
> with (local-set-key [2290] "{").

Yep, it works (on my keyboard this is 3945 for "é"). I've found this 
solution (cf "Non-ascii key binding..." thread) through 
(read-key-sequence "").

Also I've remarked this :

(kbd "é") => 233
(multibyte-char-to-unibyte 3945) => 233
(unibyte-char-to-multibyte 233) => 2281

(- (unibyte-char-to-multibyte 233) (multibyte-char-to-unibyte 3945)) => 2048

I remember to have got 2048 with a lisp function which returns the value 
to add to a unibyte to get the multibyte sequence... But what function ?

-- 
Mounir AITTAHAR

Re: Translating keys

[Mounir AITTAHAR]

I'm fed up with this 9telecom news server.

> Check some of those threads that have been running these days.
> I've recently posted an explanation of the problem along with solutions.


My server news is really rubbish.

By Google, I've read your message (hope this is this one you told
about)_:

> Try M-: (read-event) RET and then hit your ò key.  It'll return the code
> Elisp receives in response to this key (e.g. 2290).  You can then bind it
> with (local-set-key [2290] "{").


Yep, it works (on my keyboard this is 3945 for "é"). I've found this
solution (cf "Non-ascii key binding..." thread) through
(read-key-sequence "").

Also I've remarked this :

(kbd "é") => 233
(multibyte-char-to-unibyte 3945) => 233
(unibyte-char-to-multibyte 233) => 2281

(- (unibyte-char-to-multibyte 233) (multibyte-char-to-unibyte 3945)) =>
2048

nonascii-insert-offset => 2048

Interesting... I have now what i need. Except the way to make a
difference between console and (X/Xterm) mode.

-- 
Mounir AITTAHAR

Re: Translating keys [solved]

[Mounir AITTAHAR]

> (read-event) or (read-key-sequence "") => typing "é" give 3945
> (kbd "é") => 233
> (multibyte-char-to-unibyte 3945) => 233
> (unibyte-char-to-multibyte 233) => 2281

But with :

(unify-8859-on-encoding-mode 1)
(unify-8859-on-decoding-mode 1)

 > (read-event) or (read-key-sequence "") => typing "é" give 2281
 > (kbd "é") => 233
 > (multibyte-char-to-unibyte 3945) => 233
 > (unibyte-char-to-multibyte 233) => 2281

Ok ! I think it was a problem of 8859 encoding unification. But don't 
know definitely why : locale pb or emacs-related...

-- 
Mounir AITTAHAR