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#63967: 28.2; switch-to-buffer in normal window fails if minibuffer window is active Date: Sun, 11 Jun 2023 10:10:17 +0200 Message-ID: References: <83o7lo28e6.fsf@gnu.org> <0469e0cb-4f63-eb4b-1184-2dfeabdcf9e6@gmx.at> <83y1krzpoy.fsf@gnu.org> <8a540045-0f14-43cf-0515-4dcab2f68b98@gmx.at> <83jzwbz1k2.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="32131"; mail-complaints-to="usenet@ciao.gmane.io" Cc: al@petrofsky.org, 63967@debbugs.gnu.org, monnier@iro.umontreal.ca To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Jun 11 10:11:25 2023 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 1q8GAX-0008BP-OS for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 11 Jun 2023 10:11:25 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1q8GAC-00033c-Qa; Sun, 11 Jun 2023 04:11:04 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q8GAA-00032n-Py for bug-gnu-emacs@gnu.org; Sun, 11 Jun 2023 04:11:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1q8GAA-0000Hk-HN for bug-gnu-emacs@gnu.org; Sun, 11 Jun 2023 04:11:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1q8GAA-0000QT-DS for bug-gnu-emacs@gnu.org; Sun, 11 Jun 2023 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: Sun, 11 Jun 2023 08:11:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 63967 X-GNU-PR-Package: emacs Original-Received: via spool by 63967-submit@debbugs.gnu.org id=B63967.16864710331581 (code B ref 63967); Sun, 11 Jun 2023 08:11:02 +0000 Original-Received: (at 63967) by debbugs.gnu.org; 11 Jun 2023 08:10:33 +0000 Original-Received: from localhost ([127.0.0.1]:36648 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1q8G9h-0000PR-1O for submit@debbugs.gnu.org; Sun, 11 Jun 2023 04:10:33 -0400 Original-Received: from mout.gmx.net ([212.227.17.20]:55101) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1q8G9d-0000P8-S1 for 63967@debbugs.gnu.org; Sun, 11 Jun 2023 04:10:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.at; s=s31663417; t=1686471019; x=1687075819; i=rudalics@gmx.at; bh=irjTfH+TUx9PrzvIEznB0SBOyOSN/gTtka0HDBeZSr8=; h=X-UI-Sender-Class:Date:Subject:To:Cc:References:From:In-Reply-To; b=O8yLsTEZSE6+ksWMWJgQ8LdqxA1YO/QmIet+iNlDRBAk6FCEWY5ScvooppTrIroeRHC+AkV /Qr06TKTrcBWDpKfvs0+5CF2SVpLz0UeEgH28DUNSiiUebTaU+bwrwj5LUp9xznm/Sfs9r9yY ciMGvJGMRvA9jufwZl2J+Gt3oplKSxMEjj3ZUY937CxG3sdwdgSotzcZ7iAa9zXnE2s3BbYF3 zbVPY2dNIfgIBQr9O/ugpgGWaFVEJDlfAsmhbFdt6kALSsX+NxMUzeQf/KL6CWplgwY/b0qa3 nKYUHi85e7FbnDmuUzYs91EEJrBW+XnSjVQrMJzKFDbSp/boveVg== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Original-Received: from [192.168.1.100] ([46.125.249.120]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MGhyc-1qM3vF2byc-00Dmvg; Sun, 11 Jun 2023 10:10:19 +0200 Content-Language: en-US In-Reply-To: <83jzwbz1k2.fsf@gnu.org> X-Provags-ID: V03:K1:GSFuzl5AWyvhiTGor/IgedL3gKyIvpGP2NGbF3N69a6LraP9sks rEq5xDPbDFM7XcnmjW7qPa1qO4QcsjaJ1WoJqtOxjKbfzngW/R3hs993YN8I4xX+CTyLmNv aivPBpBA/LyRJJryAU4KB78CK0tM3YwBu6Tnw5TnAFZax5F2QRH++gP9dQyWQvIXvLOiwd7 kNJTq9JwdI3Bp/NYAgvFQ== UI-OutboundReport: notjunk:1;M01:P0:qkDpLxtDr+U=;Cgy6mJRyhNrW9TyBv4vcBr8fdSe AJNdoDgYrnnctGc0qIj6fc1vKrRubBMwP7+3UwVaWLE2lLV/aNzn/SLKL5Qkl07RDSA89H8Lv wtl+sKdrRA+0j0OtkvNKZ7NRi77yisvfDAMIo4/qmZxiTcd9rRkcJgNwsHzBOR283V/O0OmZQ XoWWWX2UuQebN2dTX6e6u1QwOx9ZLflACI2OqlAGYWM8hnLqYM4jZwiEpeBH6fnYwRhJrWSdK +A8Ify3eywhq7gndE5FbWmcgJ5epAqebKellJg+NgZgK3WuI3CxnuNrzIaOBKBh4wfDvBrijk /KbAbtaECno6iipJoDp2XKro7wkstGhE91feJ/J1pnnAAjummge3y/t9vpgNVgkT6QWRyaZ9A SFLVCEZJwnw1IFz4Qcm6GsxyWotq/7B7N5BorlEwltCI4c/qjxxMFKM7j6KXMsaJ9z96YdVH3 wrzLAY8ipaEzyquClDGIoVw8xCzL+UapcXUd+MLTlWCgr6o6Kf80l47QOYsoCm/JVQvgaOkri oTdl0YswMahwx1Ka/G00eGP8V+LswofywCDTw5vXXq5J/9FouTJHDEcx1hvHD4Pvi8AfosE73 IYxFqsH7KI3uACwVhJLXe/Aqm9G9FbjIpj6lbR/m+PW/18782Ng2CiWjXpDiu0bDWzYgZttB2 sCu5hRSSmw30bIPiUr7mZaiPpqJ1la4dx6hpx8m7AfOvWXIEQP+f46NTEYUHIXKTAVu4Lkvvl XogJ8Ey94QRudjFc6ic/g5H8WX0EQeVwptbVUoXLOYgexZtKRoMnkZcOqJKJOTvRcuYLsfMt 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:263242 Archived-At: >> If w->prev_buffers gets us the right minibuffer to display here (any >> former dw->prev_buffers = sw->prev_buffers should guarantee that), then >> for that buffer we have to establish the corresponding start and point >> positions. This makes sense regardless of whether the minibuffer window >> will be selected or not. > > But read_minibuf_unwind already does all that when it restores the > window configuration, doesn't it? Or is there something about the > mini-window that restoring window configuration doesn't handle > correctly? I can imagine the following scenario: read_minibuf saves and restores up to two window configurations - the one of the frame from where it was invoked and the one of the frame that owned the corresponding minibuffer window at that time. Now with 'minibuffer-follows-selected-frame' non-nil there might be another frame the user may want to continue the interaction with and the configuration of that frame will not be automatically restored upon exiting read_minibuf. Yet, the minibuffer window on that frame should be restored properly to show its previous buffer, point etc. martin