From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: steve@sanityinc.com, 19972@debbugs.gnu.org
Subject: bug#19972: Font size change doesn't update (window-total-width)
Date: Wed, 04 Mar 2015 20:59:30 +0200 [thread overview]
Message-ID: <838ufcpp0t.fsf@gnu.org> (raw)
In-Reply-To: <54F752D3.7050800@gmx.at>
> Date: Wed, 04 Mar 2015 19:45:39 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: jan.h.d@swipnet.se, steve@sanityinc.com, 19972@debbugs.gnu.org
>
> > Feel free to ignore, btw. But to clarify, what I had in mind was call
> > MoveWindow, and wait for WM_SIZE before we call change_frame_size. I
> > have no idea whether this is a good idea, though.
>
> It's not the idea that bothers me but the implementation. Looking at
> what Jan did in x_wait_for_event it seems very unlikely that I could
> come up with an equivalent solution. Think of the input un-/blocking
> part:
>
> int level = interrupt_input_blocked;
> ...
> while (f->wait_event_type)
> {
> pending_signals = true;
> totally_unblock_input ();
> /* XTread_socket is called after unblock. */
> block_input ();
> interrupt_input_blocked = level;
>
> Would this work on Windows? And on Gtk he does
>
> (void)gtk_events_pending ();
> gdk_flush ();
>
> before calling x_wait_for_event. Would we have to flush old messages on
> Windows and if so how? All this is probably over my head.
I don't see why do we have to block and wait. Why not simply go about
our business, and let the WM_SIZE message come in when it does, and be
handled?
next prev parent reply other threads:[~2015-03-04 18:59 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 2:31 bug#19972: 24.4; Font size change doesn't update (window-total-width) Joost Kremers
2015-03-01 15:14 ` martin rudalics
2015-03-01 15:28 ` Eli Zaretskii
2015-03-01 15:54 ` martin rudalics
2015-03-01 17:07 ` Joost Kremers
2015-03-01 17:46 ` Eli Zaretskii
2015-03-01 20:43 ` Joost Kremers
2015-03-02 3:30 ` Eli Zaretskii
2015-03-02 3:59 ` Joost Kremers
2015-03-02 14:04 ` Eli Zaretskii
2015-03-02 17:08 ` martin rudalics
2015-03-02 17:35 ` Eli Zaretskii
2015-03-02 18:12 ` martin rudalics
2015-03-02 18:25 ` Eli Zaretskii
2015-03-02 18:43 ` martin rudalics
2015-03-02 18:46 ` Eli Zaretskii
2015-03-02 22:26 ` Joost Kremers
2015-03-03 3:36 ` Eli Zaretskii
2015-03-03 8:07 ` martin rudalics
2015-03-03 9:06 ` Jan Djärv
2015-03-03 10:17 ` martin rudalics
2015-03-03 11:05 ` Jan D.
2015-03-03 11:26 ` martin rudalics
2015-03-03 12:08 ` Jan D.
2015-03-03 12:08 ` Joost Kremers
2015-03-03 8:06 ` martin rudalics
2015-03-02 17:08 ` martin rudalics
2015-03-02 17:07 ` martin rudalics
2015-03-02 17:06 ` martin rudalics
2015-03-01 17:06 ` Joost Kremers
2015-03-02 3:18 ` Joost Kremers
2015-03-02 17:09 ` martin rudalics
2015-03-02 17:24 ` Eli Zaretskii
2015-03-02 18:12 ` martin rudalics
2015-03-02 18:26 ` Eli Zaretskii
2015-03-03 10:38 ` martin rudalics
2015-03-03 12:23 ` Joost Kremers
2015-03-04 15:10 ` martin rudalics
2017-10-02 8:48 ` martin rudalics
2015-03-02 7:57 ` bug#19972: " Steve Purcell
2015-03-02 13:27 ` Eli Zaretskii
2015-03-02 14:07 ` Steve Purcell
2015-03-02 14:09 ` Steve Purcell
2015-03-02 14:24 ` Eli Zaretskii
2015-03-02 17:37 ` Jan D.
2015-03-02 14:23 ` Eli Zaretskii
2015-03-02 17:42 ` Jan D.
2015-03-02 17:56 ` Eli Zaretskii
2015-03-02 19:06 ` Jan D.
2015-03-02 19:52 ` Eli Zaretskii
2015-03-02 20:19 ` Jan D.
2015-03-03 16:11 ` Eli Zaretskii
2015-03-03 17:47 ` martin rudalics
2015-03-03 18:02 ` Eli Zaretskii
2015-03-03 18:36 ` martin rudalics
2015-03-03 18:38 ` Eli Zaretskii
2015-03-04 15:10 ` martin rudalics
2015-03-04 17:47 ` Eli Zaretskii
2015-03-04 18:45 ` martin rudalics
2015-03-04 18:59 ` Eli Zaretskii [this message]
2015-03-04 19:25 ` Jan D.
2015-03-05 8:06 ` martin rudalics
2015-03-05 16:34 ` Eli Zaretskii
2015-03-05 18:14 ` martin rudalics
2015-03-05 20:22 ` Eli Zaretskii
2015-03-05 21:15 ` martin rudalics
2015-03-06 8:09 ` Eli Zaretskii
2015-03-06 9:21 ` martin rudalics
2015-03-06 10:58 ` Eli Zaretskii
2015-03-02 14:44 ` Drew Adams
2015-03-02 15:02 ` Steve Purcell
2015-03-02 17:10 ` martin rudalics
2015-03-02 17:23 ` Steve Purcell
2015-03-02 18:12 ` 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=838ufcpp0t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19972@debbugs.gnu.org \
--cc=rudalics@gmx.at \
--cc=steve@sanityinc.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.