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: Wed, 14 Oct 2020 17:07:13 +0000 Message-ID: References: <20201013190255.GA8896@ACM> <838sca0w7k.fsf@gnu.org> <20201013195103.GB8896@ACM> <20201013204408.GC8896@ACM> <831ri027vz.fsf@gnu.org> <20201014160240.GA7651@ACM> <83d01kzswk.fsf@gnu.org> <20201014163534.GB7651@ACM> Reply-To: Gregory Heytings Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31829"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Alpine 2.22 (NEB 394 2020-01-19) Cc: Eli Zaretskii , emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Oct 14 19:12: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 1kSkKa-0008Ao-6W for ged-emacs-devel@m.gmane-mx.org; Wed, 14 Oct 2020 19:12:52 +0200 Original-Received: from localhost ([::1]:35470 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kSkKZ-0005j3-88 for ged-emacs-devel@m.gmane-mx.org; Wed, 14 Oct 2020 13:12:51 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43904) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kSkFI-0007ls-5g for emacs-devel@gnu.org; Wed, 14 Oct 2020 13:07:24 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:52430) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kSkFF-0001Ng-IL; Wed, 14 Oct 2020 13:07:23 -0400 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 09EH7Gw7022572 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Wed, 14 Oct 2020 17:07:16 GMT Original-Received: (from ghe@localhost) by sdf.org (8.15.2/8.12.8/Submit) id 09EH7FER028388; Wed, 14 Oct 2020 17:07:15 GMT In-Reply-To: <20201014163534.GB7651@ACM> Received-SPF: pass client-ip=205.166.94.24; envelope-from=ghe@sdf.org; helo=mx.sdf.org X-detected-operating-system: by eggs.gnu.org: First seen = 2020/10/14 13:07:19 X-ACL-Warn: Detected OS = ??? 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:257663 Archived-At: > > I'm not quite sure what a mini-window is. Does it mean the window > within which the minibuffer is displayed? As in max-mini-window-height? > The mini-window is usually at the bottom of the Emacs frame and is usually only one line tall. It does not have a mode-line. It displays the minibuffer (for interactive use, with C-x C-f, M-x, ...) and the echo area (for messages). >> So if we cannot reconcile our preferences, maybe we should have a user >> option to decide which behavior to choose. > > Perhaps. If we can formulate the two (or several) options in a > non-confusing way. This is a fairly arcane matter. > AFAIU, the possible options include at least: - keep the current behavior, with which all recursive minibuffers are moved from one frame to another when one or more minibuffers are active in one frame, and a new recursive activation happens in another frame (which happens only when enable-recursive-minibuffers is t) - move all recursive minibuffers from one frame to the other when switching to another frame - tie each one of the recursive minibuffers to the frame in which it was activated (Of course the above options only make sense when there is one miniwindow in each frame.)