From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Miha =?utf-8?B?UmlodGFyxaFpxI0=?= Newsgroups: gmane.emacs.devel Subject: Re: Stop frames stealing eachothers' minibuffers! Date: Sat, 20 Mar 2021 13:49:19 +0100 Message-ID: <87h7l6t2gg.fsf@miha-pc> References: <83sg4sbs6w.fsf@gnu.org> <694e12db-a19c-31f8-077c-62d32b640eb9@gmx.at> <83o8fgfgjn.fsf@gnu.org> <83mtuze31r.fsf@gnu.org> <838s6jdthq.fsf@gnu.org> <83im5mcd7i.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25913"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Alan Mackenzie , Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Mar 20 13:52:57 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 1lNb69-0006f1-Cc for ged-emacs-devel@m.gmane-mx.org; Sat, 20 Mar 2021 13:52:57 +0100 Original-Received: from localhost ([::1]:33800 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lNb68-0003wG-7q for ged-emacs-devel@m.gmane-mx.org; Sat, 20 Mar 2021 08:52:56 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52874) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lNb2g-0002Xl-VJ for emacs-devel@gnu.org; Sat, 20 Mar 2021 08:49:22 -0400 Original-Received: from chiru.no ([142.4.209.132]:39840) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_CHACHA20_POLY1305:256) (Exim 4.90_1) (envelope-from ) id 1lNb2f-0001ng-E1; Sat, 20 Mar 2021 08:49:22 -0400 Original-Received: from localhost (BSN-77-156-43.static.siol.net [193.77.156.43]) by chiru.no (Postfix) with ESMTPSA id 26F3E128007D; Sat, 20 Mar 2021 12:49:19 +0000 (UTC) In-Reply-To: Received-SPF: none client-ip=142.4.209.132; envelope-from=jakanakaevangeli@chiru.no; helo=chiru.no 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_NONE=0.001, SPF_NONE=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:266647 Archived-At: Alan Mackenzie writes: >> No, I'm saying that the initial frame is never deleted. At least >> that's my recollection. > > So, when a new frame is created (possibly with emacsclient), and there > are now exactly two frames, we want to copy any minibuffers from the > other frame to the new one when that other frame is the initial frame. Just giving a heads up that trouble may arise when moving a minibuffer from one terminal to another (from tty to X for example). This is judging from the following comment that I stumbled upon when reading function `server-goto-toplevel': ;; 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. `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.