[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: usr1-signal, usr2-signal, etc.
From: |
YAMAMOTO Mitsuharu |
Subject: |
Re: usr1-signal, usr2-signal, etc. |
Date: |
Thu, 14 Dec 2006 18:14:26 +0900 |
User-agent: |
Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (Shijō) APEL/10.6 Emacs/22.0.91 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI) |
>>>>> On Wed, 13 Dec 2006 11:26:53 +0100, address@hidden (Kim F. Storm) said:
>> I tried minimizing the first problem, but the second one still
>> remains.
> Thank you very much.
> The changes look good, so please install them.
Done.
>> BTW, is it necessary for us to read these events by
>> read-key-sequence? If not, it looks natural to bind them in
>> special-event-map.
> You have a good point there! If we bind signals in
> special-event-map, we don't really have to care about them being
> mixed up with the rest of the keyboard events ...
Yes. The Emacs Lisp info says:
`signal usr1'
`signal usr2'
These event sequences are generated when the Emacs process receives
the signals `SIGUSR1' and `SIGUSR2'. They contain no additional
data because signals do not carry additional information.
If one of these events arrives in the middle of a key sequence--that
is, after a prefix key--then Emacs reorders the events so that this
event comes either before or after the multi-event key sequence, not
within it.
But currently they do not behave as above.
> OTOH, if we put them in the special-event-map, we make it
> practically impossible for a (global) minor-mode to setup catching a
> signal through its "private" keymaps. So keeping signals in the
> read-key-sequence loop is definitely more flexible.
> Also, although the definition of special-event-map doesn't
> explicitly say so, it only allows bindings for single events. This
> means that we would have to revert to having just a single event for
> signals.
One possible way would be to generate an intermediate single event
that carries a signal number, and bind such an event to a dispatcher
command in special-event-map. Then the dispatcher looks up the
corresponding (multiple) key sequence and executes the associated
command. `mac-dispatch-apple-event' in term/mac-win.el handles Apple
Events in such a way so these events may not be mixed up with a usual
key sequence.
YAMAMOTO Mitsuharu
address@hidden
- Re: usr1-signal, usr2-signal, etc., (continued)
- Re: usr1-signal, usr2-signal, etc., David Kastrup, 2006/12/05
- Re: usr1-signal, usr2-signal, etc., Kim F. Storm, 2006/12/05
- Re: usr1-signal, usr2-signal, etc., YAMAMOTO Mitsuharu, 2006/12/08
- Re: usr1-signal, usr2-signal, etc., Kim F. Storm, 2006/12/11
- Re: usr1-signal, usr2-signal, etc., YAMAMOTO Mitsuharu, 2006/12/11
- Re: usr1-signal, usr2-signal, etc., Kim F. Storm, 2006/12/12
- Re: usr1-signal, usr2-signal, etc., YAMAMOTO Mitsuharu, 2006/12/12
- Re: usr1-signal, usr2-signal, etc., Kim F. Storm, 2006/12/12
- Re: usr1-signal, usr2-signal, etc., YAMAMOTO Mitsuharu, 2006/12/13
- Re: usr1-signal, usr2-signal, etc., Kim F. Storm, 2006/12/13
- Re: usr1-signal, usr2-signal, etc.,
YAMAMOTO Mitsuharu <=
- Re: usr1-signal, usr2-signal, etc., Kim F. Storm, 2006/12/14
- Re: usr1-signal, usr2-signal, etc., Chong Yidong, 2006/12/18
- Re: usr1-signal, usr2-signal, etc., YAMAMOTO Mitsuharu, 2006/12/18
- Re: usr1-signal, usr2-signal, etc., Kim F. Storm, 2006/12/19
- Re: usr1-signal, usr2-signal, etc., Kim F. Storm, 2006/12/19
- Re: usr1-signal, usr2-signal, etc., Richard Stallman, 2006/12/20
- Re: usr1-signal, usr2-signal, etc., Kim F. Storm, 2006/12/20
- Re: usr1-signal, usr2-signal, etc., Richard Stallman, 2006/12/12
- Re: usr1-signal, usr2-signal, etc., Richard Stallman, 2006/12/05
- Re: usr1-signal, usr2-signal, etc., Johan Bockgård, 2006/12/06