unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
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: Fri, 22 Apr 2016 12:10:12 +0200	[thread overview]
Message-ID: <5719F884.1010100@gmx.at> (raw)
In-Reply-To: <wlk2jrs2ai.wl%mituharu@math.s.chiba-u.ac.jp>

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

Thanks for the kind reminder.  If it weren't for you, I would have
continued to find culprits in all possible directions.

Then, Pip Zeta explicitly wrote

   I think the problem is the call to do_pending_window_change in
   xg_frame_resized in gtkutil.c:

and I apparently decided that it's time to throw out all babies with the
bathwater.

Thanks again, martin





  reply	other threads:[~2016-04-22 10:10 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
2016-04-22 10:10     ` martin rudalics [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5719F884.1010100@gmx.at \
    --to=rudalics@gmx.at \
    --cc=23320@debbugs.gnu.org \
    --cc=andlind@gmail.com \
    --cc=mituharu@math.s.chiba-u.ac.jp \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).