[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#6256: 24.0.50; read-event in `repeat' command
From: |
Stefan Monnier |
Subject: |
bug#6256: 24.0.50; read-event in `repeat' command |
Date: |
Mon, 24 May 2010 22:41:25 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) |
> I take it back. `read-char-exclusive' is not the right fix, because not all
> keyboard events are character events. Hitting the key `left', for instance,
> does not work.
I think the real answer is that both read-event and read-char-exclusive
are the wrong answer. A better answer would be to have some way to
change the way the next key is handled. Something like
a `next-key-map', kind of like the overriding maps, except that it would
be automatically reset before running a command (and it would not
disable the other keymaps, only take precedence over them).
Basically calling read-event and friends and then putting it back onto
the unread-command-events list is almost always wrong in one way or
another (e.g. it postpones running post-command-hook).
Stefan