From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#32672: 27.0.50; image resize on window resizing Date: Mon, 24 Sep 2018 20:53:07 +0300 Message-ID: <83r2hiaikc.fsf@gnu.org> References: <87pnxmyjgt.fsf@mail.linkov.net> <87ftyfoakb.fsf@mail.linkov.net> <5B98B33D.7000605@gmx.at> <871s9ycnjl.fsf@mail.linkov.net> <5B9A15DA.5000403@gmx.at> <87efdxnfww.fsf@mail.linkov.net> <5B9B7253.5060808@gmx.at> <87pnxexr2m.fsf@mail.linkov.net> <5B9E1E0E.7070805@gmx.at> <87h8ip2eby.fsf@mail.linkov.net> <5B9F4DBD.5020009@gmx.at> <877ejjzr9s.fsf@mail.linkov.net> <5BA20763.8070305@gmx.at> <875zz1t6y1.fsf@mail.linkov.net> <5BA34D7E.4030509@gmx.at> <87fty3sp6a.fsf@mail.linkov.net> <5BA490E5.5090506@gmx.at> <87zhw9xjpx.fsf@mail.linkov.net> <5BA74E3D.5030903@gmx.at> <87va6wt79n.fsf@mail.linkov.net> <5BA89ED5.4050207@gmx.at> <83in2vb8dw.fsf@gnu.org> <5BA8D7AB.5030106@gmx.at> <83d0t3awqt.fsf@gnu.org> <5BA920C4.1060204@gmx.at> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1537811529 15829 195.159.176.226 (24 Sep 2018 17:52:09 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 24 Sep 2018 17:52:09 +0000 (UTC) Cc: 32672@debbugs.gnu.org, juri@linkov.net To: martin rudalics Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Sep 24 19:52:05 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g4V1e-0003yH-VJ for geb-bug-gnu-emacs@m.gmane.org; Mon, 24 Sep 2018 19:52:03 +0200 Original-Received: from localhost ([::1]:46340 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g4V3l-0003V0-Ky for geb-bug-gnu-emacs@m.gmane.org; Mon, 24 Sep 2018 13:54:13 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35891) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g4V3d-0003Un-9h for bug-gnu-emacs@gnu.org; Mon, 24 Sep 2018 13:54:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g4V3Z-0001uu-Q9 for bug-gnu-emacs@gnu.org; Mon, 24 Sep 2018 13:54:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:48066) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1g4V3Z-0001ug-MF for bug-gnu-emacs@gnu.org; Mon, 24 Sep 2018 13:54:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1g4V3Z-0003aA-KL for bug-gnu-emacs@gnu.org; Mon, 24 Sep 2018 13:54:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 24 Sep 2018 17:54:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 32672 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 32672-submit@debbugs.gnu.org id=B32672.153781161013727 (code B ref 32672); Mon, 24 Sep 2018 17:54:01 +0000 Original-Received: (at 32672) by debbugs.gnu.org; 24 Sep 2018 17:53:30 +0000 Original-Received: from localhost ([127.0.0.1]:52324 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g4V33-0003ZL-VU for submit@debbugs.gnu.org; Mon, 24 Sep 2018 13:53:30 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:54350) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g4V31-0003Z5-4L for 32672@debbugs.gnu.org; Mon, 24 Sep 2018 13:53:28 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g4V2r-0001Sn-S0 for 32672@debbugs.gnu.org; Mon, 24 Sep 2018 13:53:21 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:39742) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g4V2r-0001Sj-Ny; Mon, 24 Sep 2018 13:53:17 -0400 Original-Received: from [176.228.60.248] (port=4378 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1g4V2q-0003oK-Ib; Mon, 24 Sep 2018 13:53:17 -0400 In-reply-to: <5BA920C4.1060204@gmx.at> (message from martin rudalics on Mon, 24 Sep 2018 19:37:08 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:150612 Archived-At: > Date: Mon, 24 Sep 2018 19:37:08 +0200 > From: martin rudalics > CC: juri@linkov.net, 32672@debbugs.gnu.org > > As I said, redisplay would not have to care about that at all. It > would simply call 'window-state-change-functions' where it calls > 'window-size-change-functions' now. And running > 'window-state-change-functions' would use one boolean set (among > others) instead of where 'run-window-configuration-change-hook' gets > called now and which it resets. Iff that boolean was set, it would > start to find all windows where a relevant change occurred and run the > functions. Buffer-locally iff a window shows the buffer for which the > local hook was set and something changed for that window. Those functions will need to keep track of the changes, or record the previous state attributes somewhere, to do their job, right? Are you saying that these are already recorded/tracked? If not, they will need to be added, which was the point I was making. > The great advantage for users and application programmers would be > that their functions would run once only and only if something really > changed since last redisplay. Even the "once" part might be problematic, because redisplay_internal sometimes re-runs its code more than once, as you know. The "really changed since last redisplay" is even trickier, because a given redisplay cycle doesn't always finish all of its job, it can stop in the middle and return after doing only part of what needs to be done, in which case some of the windows are not updated, and we will have lost our point of reference.