Subject: bug#1348: set-frame-width and set-frame-position seem buggy on at least MSWindows

From: Eli Zaretskii <[email-masked]>
Date: Wed, 03 Dec 2008 20:32:50 +0200

> Date: Wed, 03 Dec 2008 11:17:13 +0100
> From: martin rudalics <[email-masked]>
> CC: [email-masked], [email-masked], [email-masked], 
>  [email-masked]
> 
> If we think that grischka's patch is wrong, we should be able to
> give an (at least hypothetical) example why.

I don't see a need for giving an example for something that is so
blatantly wrong: it calls one thread's code from within another.
Since the Emacs input thread was written _specifically_ to overcome
problems with delivering input asynchronously, it should be clear to
anyone that mixing such threads is dead wrong, period.