From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: Stop frames stealing eachothers' minibuffers! Date: Sat, 28 Nov 2020 22:38:25 +0000 Message-ID: References: <53833023-d959-07af-7611-aa2e0bdcc1bc@gmx.at> <0d14bfc4-8e8e-d3b9-e0e1-ee4bf2e6449d@gmx.at> <20201125210947.GB8228@ACM> Reply-To: Gregory Heytings Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="-212064758-1432818827-1606602731=:18800" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18103"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Alpine 2.22 (NEB 394 2020-01-19) Cc: Andrii Kolomoiets , emacs-devel@gnu.org, martin rudalics , enometh@meer.net, Alan Mackenzie , Eli Zaretskii To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Nov 28 23:39:52 2020 Return-path: Envelope-to: ged-emacs-devel@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 1kj8si-0004cv-K8 for ged-emacs-devel@m.gmane-mx.org; Sat, 28 Nov 2020 23:39:52 +0100 Original-Received: from localhost ([::1]:48294 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kj8sh-0006Q8-KX for ged-emacs-devel@m.gmane-mx.org; Sat, 28 Nov 2020 17:39:51 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43306) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kj8rc-0005wn-KG for emacs-devel@gnu.org; Sat, 28 Nov 2020 17:38:44 -0500 Original-Received: from mx.sdf.org ([205.166.94.24]:49215) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kj8ra-0004uH-Ch; Sat, 28 Nov 2020 17:38:44 -0500 Original-Received: from sdf.org (IDENT:ghe@faeroes.freeshell.org [205.166.94.9]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 0ASMcStb020664 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Sat, 28 Nov 2020 22:38:29 GMT Original-Received: (from ghe@localhost) by sdf.org (8.15.2/8.12.8/Submit) id 0ASMd2JF023383; Sat, 28 Nov 2020 22:39:02 GMT In-Reply-To: Content-ID: Received-SPF: pass client-ip=205.166.94.24; envelope-from=ghe@sdf.org; helo=mx.sdf.org X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:259981 Archived-At: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---212064758-1432818827-1606602731=:18800 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Content-ID: >>>> Isn't the main reason for this that it has never been possible to=20 >>>> interact with a MBn when a MBm, with m > n, was active? >>> >>> Well, it's at best an indirect cause of the bug, but yes, it's the=20 >>> reason why this bug wasn't visible until now. >> >> Put another way, is it not problematic to interact with and/or=20 >> terminate a recursive edit while one or more higher level recursive=20 >> edits are underway? > > I think "interact with" should be OK (I can see situations where you'd=20 > use two minibuffers, where you copy text from one to the other), but=20 > since the invocations have to obey the nesting, exiting from the=20 > non-deepest minibuffer is indeed a problem. > Okay, so I wasn't completely wrong when I said that tying minibuffers to=20 the frames in which they are created is complex ;-) If it becomes possible to interact with lower level minibuffers, typing=20 ".emacs RET" in a lower level minibuffer that was previously created with= =20 "C-x C-f" would open the file. What would happen with the minibuffer at=20 that point? What should happen if it is entered again for example with=20 C-x o? Will it become a Schr=F6dinger minibuffer that is neither alive nor= =20 dead? >> Do you think the recipe with more than two frames I just sent=20 >> demonstrates a bug? > > If you're referring to the recipe to which I responded, then yes. > I'm not sure what you mean by "the recipe to which I responded". I meant= =20 the recipe I sent about an hour ago. ---212064758-1432818827-1606602731=:18800--