From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.bugs Subject: bug#32672: 27.0.50; image resize on window resizing Date: Mon, 24 Sep 2018 21:38:59 +0300 Organization: LINKOV.NET Message-ID: <87a7o6ewxw.fsf@mail.linkov.net> References: <87pnxmyjgt.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 X-Trace: blaine.gmane.org 1537816468 10341 195.159.176.226 (24 Sep 2018 19:14:28 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 24 Sep 2018 19:14:28 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (x86_64-pc-linux-gnu) Cc: 32672@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Sep 24 21:14:24 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 1g4WJK-0002ZX-VW for geb-bug-gnu-emacs@m.gmane.org; Mon, 24 Sep 2018 21:14:23 +0200 Original-Received: from localhost ([::1]:46611 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g4WLR-0007OP-JX for geb-bug-gnu-emacs@m.gmane.org; Mon, 24 Sep 2018 15:16:33 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33363) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g4WK2-0006c4-79 for bug-gnu-emacs@gnu.org; Mon, 24 Sep 2018 15:15:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g4WK0-0000jv-H8 for bug-gnu-emacs@gnu.org; Mon, 24 Sep 2018 15:15:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:48101) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1g4WK0-0000jf-C4 for bug-gnu-emacs@gnu.org; Mon, 24 Sep 2018 15:15:04 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1g4WK0-0005Xi-6k for bug-gnu-emacs@gnu.org; Mon, 24 Sep 2018 15:15:04 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Juri Linkov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 24 Sep 2018 19:15:04 +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.153781645921141 (code B ref 32672); Mon, 24 Sep 2018 19:15:04 +0000 Original-Received: (at 32672) by debbugs.gnu.org; 24 Sep 2018 19:14:19 +0000 Original-Received: from localhost ([127.0.0.1]:52342 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g4WJG-0005Uu-QR for submit@debbugs.gnu.org; Mon, 24 Sep 2018 15:14:18 -0400 Original-Received: from pop.dreamhost.com ([64.90.62.162]:38590 helo=pdx1-sub0-mail-a31.g.dreamhost.com) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g4WJF-0005Ul-8W for 32672@debbugs.gnu.org; Mon, 24 Sep 2018 15:14:17 -0400 Original-Received: from pdx1-sub0-mail-a31.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a31.g.dreamhost.com (Postfix) with ESMTP id 698617F96C; Mon, 24 Sep 2018 12:14:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=linkov.net; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=linkov.net; bh=00THENhPT79kx4h7/L3xe7fy56M=; b= YRXD5sqK7nmTRsAW4PzCFNU6WjiNav855t3qSpLte1j9r4AzGVvoVi3JqH/z/GSj SCoCA2ySsggSLBFPa6PsB2kOLrkJqMrgaI8Sv7J6GPeh+lHJam525OdvEiO2rncR PKqpqA27bZtwYC2L7jsRUNHu015l64CkHOxhXgGlwPc= Original-Received: from localhost.linkov.net (m91-129-111-128.cust.tele2.ee [91.129.111.128]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: jurta@jurta.org) by pdx1-sub0-mail-a31.g.dreamhost.com (Postfix) with ESMTPSA id 4D62F7F29D; Mon, 24 Sep 2018 12:14:15 -0700 (PDT) X-DH-BACKEND: pdx1-sub0-mail-a31 X-DH-BACKEND: pdx1-sub0-mail-a31 In-Reply-To: <83in2vb8dw.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 24 Sep 2018 11:35:23 +0300") 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:150619 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. I think window hook calls should be consistent at least with own inner logic, e.g. as the semantics of the window-size-change-functions hook name suggests it should be called when the window size is not the same as was before, window-configuration-change-hook is called when the result of window-state-get is not the same as it was before, etc. This poses a question what a programmer is supposed to do when a hook is more general, how to filter out the wanted notifications when the hook is fired more often than needed. We already have a working solution in form of window-pixel-width-before-size-change, that could be extended to other hooks, thus they could report the reason of their calls exposing more their meta information, e.g. window-configuration-change-hook to report that only one buffer in one particular window was switched. So either we need more specific hooks, or allow general hooks report the details inscluding the reasons of their calls.