Re: interactive closure — variables not bound

[Ricardo Wurmus <rekado@elephly.net>]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> I guessed that this odd behaviour must be a result of calling the
>> callback procedure from C with “call1”.  I thought that maybe this is
>> expected behaviour when calling a procedure that interacts with the user
>> through the mini-buffer (as read-string does) when it is not using the
>> “interactive” form.
>
> read-string works just as well from outside an interactive spec.
>
> My crystal ball tells me that it suspects the culprit is that the code
> calls the Elisp callback asynchronously, i.e. from a different thread.
> IOW it thinks that the code doesn't bother to go through the Elisp event
> queue to synchronize with the Elisp engine.

Ah, this indeed seems to be the case here!  I wasn’t aware of the Elisp
event queue.  Now that I am, I see that xwidget.c already contains code
to create events of kind “XWIDGET_EVENT”, so I’ll try to use that.

Thanks for the good hint!

~~ Ricardo