Re: System calls without error checks in w32

[Lennart Borgman <lennart.borgman@gmail.com>]

On Mon, Jun 7, 2010 at 4:54 PM, Stephen J. Turnbull <stephen@xemacs.org> wrote:
> grischka writes:
>
>  > XEmacs uses the same thread for lisp and gui and doesn't have any
>  > such problem.
>
> XEmacs has such a hairy event loop that it is no longer supported by
> X.org.  You may not want to go there.
>
> http://bugs.freedesktop.org/show_bug.cgi?id=13471
> https://trac.macports.org/ticket/18491
> http://bugs.freedesktop.org/show_bug.cgi?id=20048

;-)

I guess the idea of having two event loops/thread is not in itself
bad. If the gui thread is never blocked it can be used to convey
status information at least to the user. (You can put these in
temporary windows inside the frame for example.)

But sometimes I wonder wheter all windows really runs in the gui
threads. And why does not C-g break all looping, even those in timers
(like fontification)? And is it the same trouble on other platfoms or
is it just the w32 port that has this?

And moreover I wonder wether all messages really reach their
destinations or if something is blocking them in certain situations.
(Again, why is not C-g handled in the case above?)

And what is blocking Emacs during the time when a new frame is
created? Why is not that done asynchronously?