From: martin rudalics <rudalics@gmx.at>
To: jasonr@f2s.com
Cc: 1348@emacsbugs.donarmstrong.com, grischka <grishka@gmx.de>
Subject: bug#1348: set-frame-width and set-frame-position seem buggy on at least MSWindows
Date: Mon, 01 Dec 2008 08:28:00 +0100 [thread overview]
Message-ID: <49339200.7080603@gmx.at> (raw)
In-Reply-To: <1228089264.493327b06fd4e@webmail.freedom2surf.net>
>> 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@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)
(sleep-for 2)
(set-frame-height (selected-frame) 55)
(sleep-for 2))
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
sees there.
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
resize will happen asynchronously. But on Windows, the menu bar
automatically wraps when the frame is too narrow to contain it,
and that causes any calculations made here to come out wrong. The
end is some nasty buggy behavior, including the potential loss
of the minibuffer.
Disabling this code is either not sufficient to fix the problems
completely, or it causes fresh problems, but at least it removes
the most problematic symptom of the minibuffer becoming unusable.
[...]
*/
Given that wrapping menubars are not very frequent, it seems to me that
by now the "fresh problems" outweigh the "menubar problem", but YMMV.
martin
next prev parent reply other threads:[~2008-12-01 7:28 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 21:22 bug#1348: set-frame-width and set-frame-position seem buggy on at least MSWindows grischka
2008-11-27 13:41 ` martin rudalics
2008-11-27 17:45 ` grischka
2008-11-27 19:48 ` martin rudalics
2008-11-29 19:42 ` grischka
2008-11-30 9:19 ` martin rudalics
2008-11-30 17:40 ` grischka
2008-11-30 20:02 ` martin rudalics
2008-11-30 22:04 ` grischka
2008-11-30 22:50 ` martin rudalics
2008-11-30 23:08 ` grischka
2008-11-30 23:54 ` jasonr
2008-12-01 7:28 ` martin rudalics [this message]
2008-12-01 8:22 ` jasonr
2008-12-01 9:34 ` martin rudalics
2008-12-02 6:11 ` grischka
2008-12-02 7:42 ` jasonr
2008-12-02 14:11 ` grischka
2008-12-02 15:54 ` martin rudalics
2008-12-02 20:04 ` Eli Zaretskii
2008-12-03 10:17 ` martin rudalics
2008-12-03 18:32 ` Eli Zaretskii
2008-12-04 18:00 ` martin rudalics
2008-12-16 17:11 ` grischka
2008-12-03 0:09 ` grischka
2008-12-03 10:17 ` martin rudalics
2008-12-03 17:24 ` grischka
2008-12-03 21:41 ` Stefan Monnier
2008-12-04 17:58 ` martin rudalics
2008-12-04 23:24 ` grischka
2008-12-05 6:20 ` Eli Zaretskii
2008-12-05 15:58 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2008-12-03 21:43 grischka
2008-12-04 4:07 ` Eli Zaretskii
2008-11-17 15:06 grischka
2008-11-14 22:46 Themba Fletcher
2008-11-15 9:40 ` Eli Zaretskii
2008-11-15 10:04 ` Eli Zaretskii
2008-11-15 14:12 ` martin rudalics
2008-11-17 20:50 ` Themba Fletcher
2008-11-18 13:03 ` martin rudalics
2014-09-21 18:02 ` martin rudalics
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49339200.7080603@gmx.at \
--to=rudalics@gmx.at \
--cc=1348@emacsbugs.donarmstrong.com \
--cc=grishka@gmx.de \
--cc=jasonr@f2s.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.