From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#32672: 27.0.50; image resize on window resizing Date: Mon, 24 Sep 2018 14:25:15 +0200 Message-ID: <5BA8D7AB.5030106@gmx.at> 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> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1537791849 27720 195.159.176.226 (24 Sep 2018 12:24:09 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 24 Sep 2018 12:24:09 +0000 (UTC) Cc: 32672@debbugs.gnu.org, juri@linkov.net To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Sep 24 14:24: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 1g4PuG-00078Y-AU for geb-bug-gnu-emacs@m.gmane.org; Mon, 24 Sep 2018 14:24:04 +0200 Original-Received: from localhost ([::1]:44951 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g4PwM-0000LC-T4 for geb-bug-gnu-emacs@m.gmane.org; Mon, 24 Sep 2018 08:26:14 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57745) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g4PwD-0000KW-RC for bug-gnu-emacs@gnu.org; Mon, 24 Sep 2018 08:26:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g4PwA-0001yZ-EH for bug-gnu-emacs@gnu.org; Mon, 24 Sep 2018 08:26:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:47178) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1g4PwA-0001yS-9Q for bug-gnu-emacs@gnu.org; Mon, 24 Sep 2018 08:26:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1g4PwA-0003d2-5f for bug-gnu-emacs@gnu.org; Mon, 24 Sep 2018 08:26:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 24 Sep 2018 12:26:02 +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.153779192913909 (code B ref 32672); Mon, 24 Sep 2018 12:26:02 +0000 Original-Received: (at 32672) by debbugs.gnu.org; 24 Sep 2018 12:25:29 +0000 Original-Received: from localhost ([127.0.0.1]:51436 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g4Pvd-0003cH-DH for submit@debbugs.gnu.org; Mon, 24 Sep 2018 08:25:29 -0400 Original-Received: from mout.gmx.net ([212.227.17.21]:55831) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g4Pvc-0003bs-Es for 32672@debbugs.gnu.org; Mon, 24 Sep 2018 08:25:28 -0400 Original-Received: from [192.168.1.101] ([212.95.5.130]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MACmL-1ftjbt3vI1-00BJE1; Mon, 24 Sep 2018 14:25:21 +0200 In-Reply-To: <83in2vb8dw.fsf@gnu.org> X-Provags-ID: V03:K1:jNCfJmnFwmBNL1uYHuWIAvWvAPXvrKU18KsqppcB/0OQSQug0dw 1SxoqapfpXZzy7+rG2uy6uO8fvUSXV/fGkFjnDtnYW6akXdqZm15Cnhjv4yMzlK/bhnmilD 9CVVqhTjEppK8qGYJxHYpEuzfv9yKHnqxzGH1tR4QSCtOw4ANEqkpf4mPBQoQLEAeAVeXtP +hVDOtfe5zj3wUtSizH9Q== X-UI-Out-Filterresults: notjunk:1;V01:K0:k44q6CkQ0o8=:Q5jEyGWzNjET5TybRgKCof LxSFvqdxdMeQ/e/AjcyUFvWdXAmG64mqC75w8mQ9y+7WSp8/qWLASVAglMkLHi4V7NXZeJ1kL KHJ0xk12ECQmMtBLBNdQ4yRf/Z2suJUDLdNahUT4EhZ31JMJrv7S6jkMZDWAIjYUHSawpLVy/ 3sXQXaQZG+IP2AgzNCQhwwIvVo+p0qYogn+EQ/6B4xpn1LFHKhI38Psd5UruY7Yh9bu7GNNGb R+khn7Lf4UchNkGDDyu1rmML9NRlVe8iczKxC1MswkYUbKZONARhmW0IiwA2Tp3uA67Oi5XY4 g9l3gNpnoagBD0z+dYVwTbb2plp0Gll6dQ2w7gbgJ9BBP3Fac1Q1CNxR01lbqI/iI9AlflPu8 ZZ7ywsBrUu2tOGYICmIGmSNq243g9dXvKdZKxU1fEOIBf5oKxeBF4/x+C9tGvblQjn35YEIYI F4UVqfX+x9bRJWA6eUq6kxpSVVSVu9rQDACbKTRZMiLCvSSM6hjl0fkAA+ZfERkqVzgtzfuNx JjKCHLaLL0IUOpp246yADaaCst51kyprFmQFVqrLhwwSyX8R/wL8rLMRKQnmp5q4qUkSI6W7A VUVk9NHlnysEN6kwkH/0EZXYbWKCYkJAdtMalt6Qrp0skyloNKzWbJVTAlae5mmz/GZ0BNLXv v6WgozUkY3mJiClnooiEvAA+DCwLCFf1fCn4oG7zxuGMriotHFICzUaY41n30zlSWgxVrefAP WRa3HuXwjWtyVLv8zHTF7TcF8UgQ3Ygi20f3Om0UoBpxLyjgWjxtiS8oM0LxtC4BTO8K+JB8 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:150597 Archived-At: >> I don't know what to do. We run hooks too often and do not provide >> sufficient information when running them. Sometimes we even hide >> information when running a hook. The problem is that changing the >> current situation will have us either run even more hooks or cause >> protests when a hook is no more run where it was run before. > > I agree. I think Lisp programs that use hooks provided by > display-related code should generally expect to be called in many > unrelated situations, and do whatever it takes by themselves to detect > when it's "their" use case. Expectations or requests for more focused > hooks are impractical or even not feasible to implement, because core > code knows very little about the Lisp application which uses the hook. 'window-configuration-change-hook' is a great mess and is not display-related. What users really need IMO is a single hook say 'window-state-change-functions' that we'd call in redisplay_internal in lieu of 'window-size-change-functions'. We would run it if something in the state of a frame's root window changed (including size changes, changes of the windows' start positions and the selected window) and additionally provide a list of the differences in the frame's previous window state and the one redisplay is about to use. But such a change would be incompatible and the hook would consequently have to be run in parallel with our present hooks. martin