Re: Timing of input-method output

[phillip.lord@russet.org.uk (Phillip Lord)]

Stefan Monnier <monnier@IRO.UMontreal.CA> writes:

>> I'm guessing this is because of the location of the input-event-function
>> call. It's happening too soon, before quail has done anything to respond
>> to the keypress that will result in complex input happening.
>
> Oh, here's another random idea:
>
>    in input-event-functions, start a timer to run "right away" (i.e. at
>    the next occasion, which will be when we finish processing the
>    current key and start waiting for the next).


Oh dear, that really does seem nasty to me.

I wonder if I am going about this in the wrong way. Given that this only
happens when quail is active, is it not quail that needs hooking?
"pre-quail-command-hook" or something. Quail knows that it's about to do
something weird that is not going to signal pre-command-hook because we
are still awaiting more information before the command happens.

If it works, it would mean that input-event-functions is not really fit
for the purpose I intended and should, perhaps, be removed.

Thoughts?

Phil