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

[grischka]

Eli Zaretskii wrote:

> 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.

Clear to anyone who? Doesn't see a need or is able to read?

Actually,
        w32_read_socket()
calls
        change_frame_size() at w32term:4596
which finally calls
        run_window_configuration_change_hook() at dispnew:6414
which runs lisp code.

You will maybe agree that it makes sense to run this hook as
a consequence from a lisp call to "set-frame-width".