[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#13709: bug#13793: 24.3.50; M-x broken in viper and X
From: |
Stefan Monnier |
Subject: |
bug#13709: bug#13793: 24.3.50; M-x broken in viper and X |
Date: |
Tue, 26 Feb 2013 09:10:28 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) |
>> [ Modulo some dance à la evil-esc-mode to add/remove this binding so
>> that code that adds escape sequences to this map never bumps into the
>> [escape] mapping. ]
> Maybe one question, because I'm not too familiar with translation
> keymaps. What do you think is the best solution to this
> add-escape-sequences-to-input-decode-map-problem? The only possibility
> that comes into my mind would be to advice `define-key` so that
> `evil-normal-esc-map` is temporarily put back into `input-decode-map`.
> Is there a better way than using such an advice?
I guess an advice might work (it probably wouldn't need to put the map
back, just let-bind a variable that causes the filter function to return
evil-normal-esc-map without bothering to sit-for).
But it doesn't sound very appealing.
Maybe "enable evil-esc-mode in post-command-hook and disable it in
pre-command-hook" might work?
Stefan
- bug#13793: 24.3.50; M-x broken in viper and X, Frank Fischer, 2013/02/23
- bug#13793: 24.3.50; M-x broken in viper and X, Stefan Monnier, 2013/02/24
- bug#13709: bug#13793: 24.3.50; M-x broken in viper and X, Frank Fischer, 2013/02/25
- bug#13709: bug#13793: 24.3.50; M-x broken in viper and X, Stefan Monnier, 2013/02/25
- bug#13709: bug#13793: 24.3.50; M-x broken in viper and X, Frank Fischer, 2013/02/26
- bug#13709: bug#13793: 24.3.50; M-x broken in viper and X,
Stefan Monnier <=
- bug#13709: bug#13793: 24.3.50; M-x broken in viper and X, Frank Fischer, 2013/02/26
- bug#13709: bug#13793: 24.3.50; M-x broken in viper and X, Stefan Monnier, 2013/02/26
- bug#13793: 24.3.50; M-x broken in viper and X, Frank Fischer, 2013/02/26
- bug#13709: bug#13793: 24.3.50; M-x broken in viper and X, Frank Fischer, 2013/02/27
- bug#13709: bug#13793: 24.3.50; M-x broken in viper and X, Stefan Monnier, 2013/02/27
- Message not available
- bug#13709: bug#13793: 24.3.50; M-x broken in viper and X, Michael Kifer, 2013/02/26