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.devel Subject: Re: Stop frames stealing eachothers' minibuffers! Date: Sun, 21 Mar 2021 12:38:34 +0200 Message-ID: <83mtuwbxlh.fsf@gnu.org> References: <83o8fgfgjn.fsf@gnu.org> <83mtuze31r.fsf@gnu.org> <838s6jdthq.fsf@gnu.org> <83im5mcd7i.fsf@gnu.org> <87h7l6t2gg.fsf@miha-pc> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38516"; mail-complaints-to="usenet@ciao.gmane.io" Cc: jakanakaevangeli@chiru.no, emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Mar 21 11:39:21 2021 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 1lNvUP-0009w8-B6 for ged-emacs-devel@m.gmane-mx.org; Sun, 21 Mar 2021 11:39:21 +0100 Original-Received: from localhost ([::1]:52238 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lNvUO-0002bc-Af for ged-emacs-devel@m.gmane-mx.org; Sun, 21 Mar 2021 06:39:20 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53076) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lNvTc-0002CO-Lc for emacs-devel@gnu.org; Sun, 21 Mar 2021 06:38:32 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:37876) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lNvTc-0002mx-As; Sun, 21 Mar 2021 06:38:32 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:4783 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1lNvTb-0001Ij-Hu; Sun, 21 Mar 2021 06:38:31 -0400 In-Reply-To: (message from Alan Mackenzie on Sun, 21 Mar 2021 10:30:39 +0000) 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:266692 Archived-At: > Date: Sun, 21 Mar 2021 10:30:39 +0000 > From: Alan Mackenzie > Cc: Eli Zaretskii , emacs-devel@gnu.org > > > ;; We're inside a minibuffer already, so if the emacs-client is trying > > ;; to open a frame on a new display, we might end up with an unusable > > ;; frame because input from that display will be blocked (until exiting > > ;; the minibuffer). Better exit this minibuffer right away. > > That looks like a bug which ought to be fixed, but I've no idea where to > start looking for the problem. It's a "feature" we only allow a single frame to be in the "input" state at any given time. > > `emacsclient ~/foo' causes a throw to top-level in most cases before > > spawning a new frame to avoid some trouble, but I'm not sure if this > > trouble applies for our case. > > When starting emacsclient, I've seen minibuffers being preserved, but I > think I've also seen them being aborted. By trouble, I think you mean > that described in the comment above. I confess that I don't have a clear idea of what is the problem you are trying to solve in the context of this discussion. Why do you want to "move" the minibuffer when emacsclient starts a new frame (or is it when it closes a frame?), and what does "move" mean in this context?