From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#55412: 28.1; In Emacs 28.1, using ':eval' in 'frame-title-format' doesn't work properly Date: Fri, 20 May 2022 10:23:17 +0200 Message-ID: <408f7b88-2000-bd10-bd9d-4e06018e8ff0@gmx.at> References: <838rr4kq56.fsf@gnu.org> <87d23565-b8ba-3b08-0d10-068be3b0c5fd@gmx.at> <83leuzf4zk.fsf@gnu.org> <83sfp6eskr.fsf@gnu.org> <83mtfeeqc5.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38212"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 55412@debbugs.gnu.org, tanzer@swing.co.at To: Eli Zaretskii , Alan Mackenzie Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri May 20 10:25:02 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nrxwS-0009nF-N2 for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 20 May 2022 10:25:00 +0200 Original-Received: from localhost ([::1]:39796 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nrxwR-0004A0-Ja for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 20 May 2022 04:24:59 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41344) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nrxvX-00048p-7s for bug-gnu-emacs@gnu.org; Fri, 20 May 2022 04:24:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:43599) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nrxvW-0004rn-Iy for bug-gnu-emacs@gnu.org; Fri, 20 May 2022 04:24:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nrxvW-0003o4-F5 for bug-gnu-emacs@gnu.org; Fri, 20 May 2022 04:24: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: Fri, 20 May 2022 08:24:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 55412 X-GNU-PR-Package: emacs Original-Received: via spool by 55412-submit@debbugs.gnu.org id=B55412.165303503214580 (code B ref 55412); Fri, 20 May 2022 08:24:02 +0000 Original-Received: (at 55412) by debbugs.gnu.org; 20 May 2022 08:23:52 +0000 Original-Received: from localhost ([127.0.0.1]:37493 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nrxvM-0003n3-3N for submit@debbugs.gnu.org; Fri, 20 May 2022 04:23:52 -0400 Original-Received: from mout.gmx.net ([212.227.15.19]:39685) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nrxvF-0003mC-Tp for 55412@debbugs.gnu.org; Fri, 20 May 2022 04:23:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1653035002; bh=HEW5B1mGM+B7DYUklbqfNFrgZeaxonho3gosEdDQG9Y=; h=X-UI-Sender-Class:Date:Subject:To:Cc:References:From:In-Reply-To; b=Qp5Abe2jguWJlfV4RD6tAz3jzTnpOWGFgPi31oUTTL8eDXAwQLrMowCjl1GMNeNqc hKk9GHBFJhC1WHrtGI2fZPIQ7uHoU5AEWSJrpw5ahKksJHLMRxbPINjqQspIbO/u+B sLfMgwyvQ44ApNOJHQXELFGIU7lojy9z98p9zEpE= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from [192.168.1.102] ([212.95.5.124]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MiaY9-1nLOBE3GIJ-00fmpm; Fri, 20 May 2022 10:23:19 +0200 Content-Language: en-US In-Reply-To: <83mtfeeqc5.fsf@gnu.org> X-Provags-ID: V03:K1:SjpcB9gpuca8GmBO4FDwEcpRGG2J93itpMUv6jTmtwgePhTCXEG Nq9dYdMzvVah1pnJTpsoApxrXNvUdBuBlz9lBGjGPa4CIkPVk4DKqaEktumvrHg7NXCXRd8 GiyRruY/K//hP/DQLNgOM2ZynaRwTa2gjMueIpsLYUHpdj4WnjjHAjNz6+L+0yu94wYW+Tt lv5HaZbZFfIGpYR1oTxNw== X-UI-Out-Filterresults: notjunk:1;V03:K0:8McwQb51cx8=:IPLSVTx6eP4aAhe5Sw1rE1 Fbmm2dRCaL5TdJSHcbHX990/ApEAt34VmFfluWdzm2oj/Gm8P0W1gwkPZXyFdgjib0dnKLoAV ILtZUhj/YQZflmlZE6BeyK5QF9KhDf0hmoeHrORylsfKlrEB38vnlTaQEFJNBVItndkOU5WZG /+1s+h4CP0yYhSVuJrRA/w8bty87dt9q2a7emAonLXt34m+DXfW5AwvW0Z4UDJ8P3JceFUf3T 5Zpjf5aen94tdW9/QyBl5tLv+9oKJN1DhY6LZdcsIYhDHYGzfwqsflU4BHuw2M+OYJmUrO+g2 pwxltI9wAgm5+LHdMmcAUuC0IEOczmBPT4Ivxb6v0J31Tp5KOYJs8HQ7ztc3H9dLaMe28zH8I YL+rau1QxjxYAUA7+UuEWtvp0rZo21PUPbIqmOHsdw9XvoTwECOeKn7S1xUJaBEvw0laSfpU/ Lxfhc1RG0HhueNm4HCCox0NivrGE4ItAAyAvgpaXJ6VPRqWDO578iyHPStxaxhHcjHWRbh3s3 uGlN6Ug7CMzkHscHva18OvaCXhLgO/P6daQPTUytFAqUMJffKR7FL1JPqbg35WkYW6eMeHa2Z QhxNs94mXBN1FSDZKioz/c8kd0jE4tGj90HZUyLQim3MgX41hv7Vj8lu2aeVkoVshnz+vvk1z +C256DkhHy20iw+ajrMDzpM5gqd3PhWDoJ4Ijmh8axvVtK7x51kn6VXCtK+L5PSggCRI9AgSl 8NpPilvNuafDOHk+qEY7Ly8bhl+EFM4a9SKLUtKHklSyYjWONlsaUpR0dnR9HtLP7UPjrcJv X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:232708 Archived-At: > It would be good to have some of these explanations in comments there. I understand that we want a quick solution for the present bug so it can be included in Emacs 28.2. But I still don't understand why nobody even cared to try the patch I sent earlier. With the current code, whenever there are at least two frames present, 'gui_consider_frame_title' calls via Fselect_window among others redisplay_other_windows Fredirect_frame_focus resize_mini_window move_minibuffers_onto_frame and sets last_nonminibuf_frame internal_last_event_frame Has anyone ever tried to understand the implications of all these? Why should redisplay indiscriminately set 'windows_or_buffers_changed' when recomputing the frame title? Why should we try to redirect frame focus which is already sufficiently hairy by itself so hardly anyone really understands what it does. Why should formatting the frame title try to resize a mini window or move minibuffers onto the selected frame? Why set last_nonminibuf_frame which might affect 'display-buffer' and apparently relies on some internal kludgery to set it precisely to the same value it had before title line formatting started. And why reset internal_last_event_frame which also appears complicated enough to not touch it unless you know precisely why and when. Similar things happen with mode lines display - unwind_format_mode_line apparently can call Fselect_window up to three times in a row with the implications sketched above. When trying to fix Bug#32777 I spent some time investigating these issues but never found out why on earth we should call routines like 'select-frame' and 'select-window' from redisplay. If there is any rationale for these, it should be explained in comments first before moving on to explain why moving minibuffers between frames can go awry. martin