From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame Date: Mon, 11 Jul 2022 19:43:11 +0300 Message-ID: <83fsj7zjkw.fsf@gnu.org> References: <5d86d890-9a2e-e4d6-13fb-da03285ea003@gmx.at> <61fe102b-eec2-9711-560e-c141ed3cc6e4@gmx.at> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4596"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rudalics@gmx.at, 56305@debbugs.gnu.org, monnier@iro.umontreal.ca, acm@muc.de To: Alan Mackenzie Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Jul 11 18:47:07 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 1oAwYr-0000sW-Ay for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 11 Jul 2022 18:47:05 +0200 Original-Received: from localhost ([::1]:49404 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oAwYp-0001zY-SA for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 11 Jul 2022 12:47:03 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34672) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oAwVu-0000pc-8Z for bug-gnu-emacs@gnu.org; Mon, 11 Jul 2022 12:44:07 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:46970) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oAwVt-0004jw-Tn for bug-gnu-emacs@gnu.org; Mon, 11 Jul 2022 12:44:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oAwVt-00068w-Pk for bug-gnu-emacs@gnu.org; Mon, 11 Jul 2022 12:44: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, 11 Jul 2022 16:44:01 +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.165755782023566 (code B ref 56305); Mon, 11 Jul 2022 16:44:01 +0000 Original-Received: (at 56305) by debbugs.gnu.org; 11 Jul 2022 16:43:40 +0000 Original-Received: from localhost ([127.0.0.1]:40867 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oAwVQ-00067v-9z for submit@debbugs.gnu.org; Mon, 11 Jul 2022 12:43:39 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:48100) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oAwVO-00067i-Lr for 56305@debbugs.gnu.org; Mon, 11 Jul 2022 12:43:31 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:56302) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oAwVI-0004YG-NH; Mon, 11 Jul 2022 12:43:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=u1CPbWpIuqS8ciBEW5/nKyOfLWgOc4ibbNW+C7v+G1Y=; b=h1b1ibPD27KJ r9Hu1RtmYlKpYGcfbw/LkPzxzI66RBSc4pTXvOjZvpNnRBgnk9qnBa6TBFNubMEg9r6tTIFOlIJPf jbd1KzohzZmUbijOidcVn4QAwQLwHfZVRkaPAv8xpSiqdFJaZJ1SL35aT6JM8YatjIT00Lo7ayIr/ +28PMqooHnhDJjXJLfdtx/ns36m9VnCAf2ylJ8kapGI55yR5BcWSho3rWChg4uPPh1QS10WXs55Ft LvOfdOhszmYjd/7Ul5LlQYmtQADblYVwgfaQ5AzpsgCpkivb8/ZVwrFuVWKICOiRHGcNVDvaQy/Lk rnwAQa73qMdvaxgYrayM2g==; Original-Received: from [87.69.77.57] (port=2911 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oAwVI-00073S-6E; Mon, 11 Jul 2022 12:43:24 -0400 In-Reply-To: (message from Alan Mackenzie on Mon, 11 Jul 2022 16:22:21 +0000) 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:236702 Archived-At: > Date: Mon, 11 Jul 2022 16:22:21 +0000 > Cc: Eli Zaretskii , monnier@iro.umontreal.ca, > 56305@debbugs.gnu.org, acm@muc.de > From: Alan Mackenzie > > > So you implemented 'minibuffer-follows-selected-frame' despite the fact > > that multiple frames hardly make sense on your usual setup? > > That's not a fact. I typically run with several/many frames on my tty. > Six, or even nine, is not uncommon. I switch between them using the > keys. The minibuffer not staying in "its own" frame was annoying > me quite a bit. I hope you'll agree that focus redirection is not very relevant to TTY frames. There, the top-most frame is the only one visible, and by definition it has the focus. > > Note that sometimes selecting a window is not enough to show it, or > > make its frame the top-most frame on display: you may also need to > > raise the frame or make sure input focus is directed to that frame. > > That sounds like the text from a bug report. Selecting a window should > either do all these GUI things, or it shouldn't do them. "Sometimes" > feels like an apology for failing to fix a bug before a release. Please don't forget that Emacs is not entirely in control of what happens here: the window manager is also an important part of this dance, and it has its own ideas about which frame should be raised and which should be given focus. It is unreasonable to expect Emacs to be able to work around every idiosyncratic aspect of the behavior of every window manager, let alone customized by users. > > wouldn't make sense if in a majority of cases selecting a window would > > _not_ also raise its frame and direct input focus to it. > > So why can't we make select-window _always_ raise its frame and get > input focus? Because it's wrong! If I want to type into a window, it does NOT mean I want that window's frame raise! Imagine a situation where I look at some text in one frame and type something into another frame: I can legitimately want to see all of the text I'm reading, but only a small portion of the text into which I'm writing. Automatically raising a frame in this case would be an annoyance, since each time I move the focus into the "typing" frame, it would raise and obscure my "reading" frame.