GNU bug report logs - #13793
24.3.50; M-x broken in viper and X

Previous Next

Package: emacs;

Reported by: Frank Fischer <frank-fischer <at> shadow-soft.de>

Date: Sat, 23 Feb 2013 18:51:02 UTC

Severity: important

Merged with 13709, 13739

Found in version 24.3.50

Done: Glenn Morris <rgm <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Frank Fischer <frank-fischer <at> shadow-soft.de>
To: Stefan Monnier <monnier <at> IRO.UMontreal.CA>
Cc: 13793 <at> debbugs.gnu.org, 13709 <at> debbugs.gnu.org, Michael Kifer <kifer <at> cs.stonybrook.edu>
Subject: bug#13793: 24.3.50; M-x broken in viper and X
Date: Wed, 27 Feb 2013 18:59:36 +0100
On 02/26, Frank Fischer wrote:
> 
> Sounds good to me. At least, I can't think of a problematic situation,
> currently. Let's how it works in practise.

Ok, now I have problem. The keymap `input-decode-map` is
keyboard-local (according to the documentation). This means (and this
makes sense because the ESC prefix map in `input-decode-map` is
different for each keyboard) we have to 'patch' it for each new
keyboard. Unfortunately, I'm not sure how to do this right.
Currently I use an `after-make-frame-functions` hook and a
`delete-terminal-functions` hook (although the latter may not be
required) to save the original prefix map in the terminal parameter
`evil-esc-map` and change `input-decode-map` accordingly. I hope that
this sets the correct values for each "keyboard".

Is this the correct way to do? Or is it completely wrong ;)

Best regards,
Frank




This bug report was last modified 8 years and 36 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.