bug#1348: set-frame-width and set-frame-position seem buggy on at least MSWindows
martin rudalics <rudalics <at> gmx.at>
2008-12-01 07:28:00 GMT
>> The wrapping menubar problem is one of the w32 API - it's nothing we can
>> do about. Personally, I considered Jason's reaction too drastic.
> Please explain. This is my first contribution to this thread, so obviously you
> are talking about something in the distant past which my memory cannot recall.
As Eli explained earlier, this thread is a consequence of your change
2007-10-09 Jason Rumney <jasonr <at> gnu.org>
* w32term.c (x_set_window_size): Disable code that attempts to tell
Lisp code about a size change before it actually happens.
which causes, according to the OP, a sequence of frame changes like
(set-frame-position (selected-frame) 0 0)
(sleep-for 2) ; not originally in my .emacs -- testing only
(set-frame-width (selected-frame) 150)
(set-frame-height (selected-frame) 55)
to virtually do the first operation only. According to grischka
something similar happens on X/GTK as well, but he never told us what he
IIUC your change is motivated as
/* The following mirrors what is done in xterm.c. It appears to be
for informing lisp of the new size immediately, while the actual