From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.devel Subject: Re: How about making `set-minibuffer-window' obsolete? Date: Thu, 18 Mar 2021 11:46:57 +0000 Message-ID: References: <838s6ndjon.fsf@gnu.org> <83y2emc500.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9253"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Mar 18 12:50:17 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 1lMrAP-0002JV-Cx for ged-emacs-devel@m.gmane-mx.org; Thu, 18 Mar 2021 12:50:17 +0100 Original-Received: from localhost ([::1]:40054 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lMrAO-0003VP-AP for ged-emacs-devel@m.gmane-mx.org; Thu, 18 Mar 2021 07:50:16 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48182) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lMr7H-0001jK-Ea for emacs-devel@gnu.org; Thu, 18 Mar 2021 07:47:03 -0400 Original-Received: from colin.muc.de ([193.149.48.1]:22920 helo=mail.muc.de) by eggs.gnu.org with smtp (Exim 4.90_1) (envelope-from ) id 1lMr7E-0003CS-9O for emacs-devel@gnu.org; Thu, 18 Mar 2021 07:47:03 -0400 Original-Received: (qmail 73658 invoked by uid 3782); 18 Mar 2021 11:46:58 -0000 Original-Received: from acm.muc.de (p4fe15597.dip0.t-ipconnect.de [79.225.85.151]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Thu, 18 Mar 2021 12:46:58 +0100 Original-Received: (qmail 19555 invoked by uid 1000); 18 Mar 2021 11:46:57 -0000 Content-Disposition: inline In-Reply-To: <83y2emc500.fsf@gnu.org> X-Submission-Agent: TMDA/1.3.x (Ph3nix) X-Primary-Address: acm@muc.de Received-SPF: pass client-ip=193.149.48.1; envelope-from=acm@muc.de; helo=mail.muc.de 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_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:266561 Archived-At: Hello, Eli. On Wed, Mar 17, 2021 at 14:57:19 +0200, Eli Zaretskii wrote: > > Date: Tue, 16 Mar 2021 20:50:17 +0000 > > Cc: emacs-devel@gnu.org > > From: Alan Mackenzie > > > I'd object to obsoleting a command just because it can be dangerous > > > when used unwisely. > > Every use of this command is unwise. It cannot possibly do anything > > useful. It can only cause problems. > I don't think I agree, not in this general form anyway. The C code > assigns values to minibuf_window in several places; this function is > the Lisp counterpart of that. If the C code can assign that variable, > why cannot Lisp code do the same if it needs to? The C code does it only under very carefully controlled circumstances (such as when iconising a frame). > With the current tendency to move stuff from C to Lisp, it is even > less understandable why would you think this function's use in unwise. > If you have specific reasons for that, please describe them in more > detail. > > Could I ask you, please, to reconsider? > I might -- if I see some specific reasoning. I didn't see that yet. OK. set-minibuffer-window, as it stands, has no function. Maybe as an alternative to obsoleting it, we could give it functionality - the function could move an open minibuffer from one frame to another frame, for example. But I'm not sure what the use case is. All the minibuffer-follows-selected-frame stuff is done internally in minibuf.c. -- Alan Mackenzie (Nuremberg, Germany).