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#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame Date: Tue, 19 Jul 2022 10:09:59 +0200 Message-ID: <6986ae82-8d4e-7675-77e9-2dc9d8e3477b@gmx.at> References: <5d86d890-9a2e-e4d6-13fb-da03285ea003@gmx.at> <61fe102b-eec2-9711-560e-c141ed3cc6e4@gmx.at> <171bab25-5eb2-884b-5c32-bcfe4fed21cc@gmx.at> <11e7e566-f626-fcf4-adfc-d03efa0d861c@gmx.at> 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="26881"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Alan Mackenzie , Eli Zaretskii , 56305@debbugs.gnu.org To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Jul 19 10:11:52 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 1oDiKe-0006oj-3l for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 19 Jul 2022 10:11:52 +0200 Original-Received: from localhost ([::1]:50842 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oDiKc-0005mt-3d for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 19 Jul 2022 04:11:50 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54756) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oDiJq-0005j9-SO for bug-gnu-emacs@gnu.org; Tue, 19 Jul 2022 04:11:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:54971) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oDiJq-0004np-Iy for bug-gnu-emacs@gnu.org; Tue, 19 Jul 2022 04:11:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oDiJq-0008R6-EV for bug-gnu-emacs@gnu.org; Tue, 19 Jul 2022 04:11: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: Tue, 19 Jul 2022 08:11:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56305 X-GNU-PR-Package: emacs Original-Received: via spool by 56305-submit@debbugs.gnu.org id=B56305.165821821132199 (code B ref 56305); Tue, 19 Jul 2022 08:11:02 +0000 Original-Received: (at 56305) by debbugs.gnu.org; 19 Jul 2022 08:10:11 +0000 Original-Received: from localhost ([127.0.0.1]:52726 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oDiJ0-0008N6-Lh for submit@debbugs.gnu.org; Tue, 19 Jul 2022 04:10:10 -0400 Original-Received: from mout.gmx.net ([212.227.17.22]:48279) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oDiIy-0008Me-8g for 56305@debbugs.gnu.org; Tue, 19 Jul 2022 04:10:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1658218200; bh=troCrIqGROW9dzXRSCnvx9P46DfmP5fuerFjlEbgvnI=; h=X-UI-Sender-Class:Date:Subject:To:Cc:References:From:In-Reply-To; b=Ow+gDhiVvJxFxzSzzKgGgMIHdkYiJCcMJHbf0jsquV8aMJ0xwHvQEGfH0ryWJ/8ub Oe4XXSTHoThaZBZMuk0Y1yFCVJNf8C2lHUzQ3ZzGPR8Hm3jmtE7aW18wQAdbWIptex wj6AFqim12o+8U8CFqHUyxrFMeRpChx7bSYbL02Q= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from [192.168.1.102] ([212.95.5.23]) by mail.gmx.net (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MV63q-1o39e20u2A-00S9Sd; Tue, 19 Jul 2022 10:10:00 +0200 Content-Language: en-US In-Reply-To: X-Provags-ID: V03:K1:a32X2COHJQbmfFhM/WU21dsBOQVQ/rnip0S+T8caRxMiq+sRk9b V+LthDn9lCqNGfE0WyTGF1B5EEsfkpwgFvV2fiy+jLC2NeXOiPUW7IAmaKRbuVNJRb6i8RE TKMwIfGb2xtj4N7xgxPJidaEK9fBfYXSdqiIXGEFEKKH7Sd4VNBKmk8E30jqngvD3aNR30L R9Om7kgNyqQukcwRb+IwQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:onuEl3lXuso=:xif8pZg6ePjEylIVDJGJfT QpR9V7N3Sn6Qj97mgAn3FuiVOy1dgaX/uiOemqPUAt67Z1ubSQmjrI5vZ56FaaA/XJ3rc9cMf /aVrfcTGhLL6rZiE/RyuiqA6z4w65fn6V0JhWF8K0/E6jdr8SmEXcq9bScTzWnaTERB6wv30x uyfkBZvNOxVvIVAv6ocP2798tYewrLBAQsZqezEKvOeIuq+2TOFyb9vdczUJlJavGP3p2Nahw omTdmdh78mu4OUKEVh8vVHcZzlkj9L/cG85m+lx/PxqlQSURnjBmRf9ZttA3Lz8l9T93QjVpJ MHgluFdKoup3NLkJY23HVmgFWl+Z3ce9aol7EWK543OqK22vGZbWcxr+OKUwORnuH940yVdGs WRmA4kUkjhWBGik0mUvTj1myPefKdOhgnGzwHqWH6mCrOAdFV7oc4PJsPhLNjthBbgKP7XNjP AIF8q7Dof3dGI+0cffIWTT3SkJupzdo/QuWRsktHMtZEOpA7146FasN/YKlbBbLqXgDJ32ywz H/h8pp+9Iuop9LYvPL/hZrE64Pn2F+lk4LIeXibaZLDc36QsZoBhuZJ1JeZ1foklP7h63ZYVX VZgM8XsQvbbVXomkJxEqg0bIC0qEyHWw7HOVfiI/f2PgneO0P8zal3rh0NArT9FP5t0+1yy+Z tHWS7QqJuBBcwgP8AY39kHGJIo3J2eO4mF9ie267asvQPDKB+N3RrOUMD8QG3zCzunS74o444 hBSS+iM10H4LO1i4f61tAeG4heoHwdpSFxDwDqtgK6NRhfKvZJJn2aBoVuxAk0g9ZfrfF3U4 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:237408 Archived-At: >>> In case you intend to fix this apparent blunder of mine: the point of >>> that commit was to set the selected window and frame so that ELisp code >>> run from the `mode-line-format` would see meaningful and consistent >>> values of selected-frame/window (and companions like the >>> frame-selected-window of the selected-frame, ...). >> How are display_mode_line or display_mode_lines affected by that commit? > > I'm sorry, I don't understand the question. Above you said that "the point of that commit was to set the selected window and frame so that ELisp code run from the `mode-line-format` would see meaningful and consistent values ...". The C functions that evaluate 'mode-line-format' for redisplay are display_mode_lines and display_mode_line and those functions did set the selected window and frame before that commit and continued to do so after your commit in the same way. FWICS your commit changed the behavior of formatting frame titles only. >> Worse even: People who want to know, for example, whether the mode line >> belongs to the selected window have to use 'old-selected-window' for >> getting that. > > Not sure "worse" than what. Worse than being "misleading". > Clearly when computing the mode-line, there are 2 windows of interest: > the one to which this mode-line belongs and the one that's currently > considered (from the outside) as "the selected window". Only one of the > two can be "the selected window" while computing the mode-line, and in > my experience most code wants/needs this to be the mode-line's window > rather than "the one that's currently considered (from the outside) as > the selected window". "The selected window is the window in which the standard cursor for selected windows appears." I see no outside POV here. And once more: I don't ask to change this design but at least to tell users about it. >> NORECORD is not about focus. > > Then we need something like it but to say "I just want to change > selected-window temporarily, so don't mess with focus or any such thing". Say to whom and where? martin