all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: martin rudalics <rudalics@gmx.at>
Cc: 23320@debbugs.gnu.org, Anders Lindgren <andlind@gmail.com>
Subject: bug#23320: 25.0.92; Window width not updated after frame resize (Win32 and GTK)
Date: Thu, 21 Apr 2016 19:07:33 +0900	[thread overview]
Message-ID: <wlk2jrs2ai.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <571788DC.20001@gmx.at>

>>>>> On Wed, 20 Apr 2016 15:49:16 +0200, martin rudalics <rudalics@gmx.at> said:

> You can find the gory details here:

> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21380

> The corresponding commit is:

> commit 8af8355c3f72500986f6f10b62714b228d6f35ee
> Author: Martin Rudalics <rudalics@gmx.at>
> Date:   Mon Aug 31 11:09:22 2015 +0200

>      Don't call do_pending_window_change in signal handlers (Bug#21380)

>      * src/gtkutil.c (xg_frame_resized):
>      * src/xterm.c (x_set_window_size):
>      * src/w32term.c (x_set_window_size): Don't call
>      do_pending_window_change.

xg_frame_resized is certainly called from the read_socket_hook
context, and it seems to be a bad idea to call
do_pending_window_change there.  But does that really apply to
x_set_window_size?

				     YAMAMOTO Mitsuharu
				mituharu@math.s.chiba-u.ac.jp





  parent reply	other threads:[~2016-04-21 10:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20  9:16 bug#23320: 25.0.92; Window width not updated after frame resize (Win32 and GTK) Anders Lindgren
2016-04-20 13:49 ` martin rudalics
2016-04-20 15:06   ` Eli Zaretskii
2016-04-21  9:15     ` martin rudalics
2016-04-21 14:19       ` Eli Zaretskii
2016-04-22 10:10         ` martin rudalics
2016-04-21 10:07   ` YAMAMOTO Mitsuharu [this message]
2016-04-22 10:10     ` martin rudalics
2016-04-22 10:10 ` martin rudalics
2016-07-01  6:13   ` 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=wlk2jrs2ai.wl%mituharu@math.s.chiba-u.ac.jp \
    --to=mituharu@math.s.chiba-u.ac.jp \
    --cc=23320@debbugs.gnu.org \
    --cc=andlind@gmail.com \
    --cc=rudalics@gmx.at \
    /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.