From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii <eliz@gnu.org> Newsgroups: gmane.emacs.bugs Subject: bug#69056: 30.0.50; history-add-new-input and recursive minibuffers Date: Fri, 16 Feb 2024 09:08:52 +0200 Message-ID: <86y1bkvqbf.fsf@gnu.org> References: <m11q9jngho.fsf@dazzs-mbp.home> <jwvplwxah1w.fsf-monnier+emacs@gnu.org> <m1v86pln1l.fsf@dazzs-mbp.home> <jwvwmr58vth.fsf-monnier+emacs@gnu.org> <m17cj5woyq.fsf@dazzs-mbp.home> <jwv8r3l8rkx.fsf-monnier+emacs@gnu.org> <86zfw1v7wu.fsf@gnu.org> <jwvr0hd7blx.fsf-monnier+emacs@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18321"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 69056@debbugs.gnu.org, me@eshelyaron.com To: Stefan Monnier <monnier@iro.umontreal.ca> Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Feb 16 08:12:01 2024 Return-path: <bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org> Envelope-to: geb-bug-gnu-emacs@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 <bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org>) id 1rasO9-0004cJ-5F for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 16 Feb 2024 08:12:01 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from <bug-gnu-emacs-bounces@gnu.org>) id 1rasNs-0006xN-30; Fri, 16 Feb 2024 02:11:44 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1rasNq-0006x7-Rr for bug-gnu-emacs@gnu.org; Fri, 16 Feb 2024 02:11:43 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1rasNq-0008Do-Ii for bug-gnu-emacs@gnu.org; Fri, 16 Feb 2024 02:11:42 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1rasO9-000536-Kv for bug-gnu-emacs@gnu.org; Fri, 16 Feb 2024 02:12:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii <eliz@gnu.org> Original-Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org> Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 16 Feb 2024 07:12:01 +0000 Resent-Message-ID: <handler.69056.B69056.170806749619376@debbugs.gnu.org> Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 69056 X-GNU-PR-Package: emacs Original-Received: via spool by 69056-submit@debbugs.gnu.org id=B69056.170806749619376 (code B ref 69056); Fri, 16 Feb 2024 07:12:01 +0000 Original-Received: (at 69056) by debbugs.gnu.org; 16 Feb 2024 07:11:36 +0000 Original-Received: from localhost ([127.0.0.1]:57801 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces@debbugs.gnu.org>) id 1rasNj-00052S-Sr for submit@debbugs.gnu.org; Fri, 16 Feb 2024 02:11:36 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:52620) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <eliz@gnu.org>) id 1rasNh-00052D-1W for 69056@debbugs.gnu.org; Fri, 16 Feb 2024 02:11:34 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <eliz@gnu.org>) id 1rasLB-0007Zl-5S; Fri, 16 Feb 2024 02:08:57 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=cDQi7O6/pONbdgXweKp+Nogv7+jLy9jqlUaFufnPfrA=; b=kmGAeQT1r/ut zQg/UcBKAjdgNytuqzuQkpzygwja54tF4z3Mgp18BfmOZpDDdwbRKQhESJtjiZesX6TDPfd2/rjUZ oVZliWQ1xu2jiXMJ1SrvXOh9E1IWfQBm62aqaVMLMf/ljwfCIgP4sgFDtwqU/AUTCXWkn+5On5JWM f4HUyMfOQPva6ltp9bj/T6DTCsBM6fSrvd9JGXXU6ybe3drd2+lAUqc0TA0fXXxFVw3CytxkNfVMl BpS8MgSZ+26m3Yhsyny7EBCbwPLuSyD/T87b9iP/laG+DyZ6O6mbSC9uycxHRrYYk/XTE1pTZhj6w a9HGvHnV3TSe2qiu2sJzGQ==; In-Reply-To: <jwvr0hd7blx.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Thu, 15 Feb 2024 14:54:07 -0500) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs.gnu.org> List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-gnu-emacs>, <mailto:bug-gnu-emacs-request@gnu.org?subject=unsubscribe> List-Archive: <https://lists.gnu.org/archive/html/bug-gnu-emacs> List-Post: <mailto:bug-gnu-emacs@gnu.org> List-Help: <mailto:bug-gnu-emacs-request@gnu.org?subject=help> List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-gnu-emacs>, <mailto:bug-gnu-emacs-request@gnu.org?subject=subscribe> Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:280090 Archived-At: <http://permalink.gmane.org/gmane.emacs.bugs/280090> > From: Stefan Monnier <monnier@iro.umontreal.ca> > Cc: me@eshelyaron.com, 69056@debbugs.gnu.org > Date: Thu, 15 Feb 2024 14:54:07 -0500 > > > for very little gain. The more general issue with let-binding > > variables around APIs that enter the minibuffer stays, so I see little > > I agree that it would be good to tackle this more general problem. > > Basically, should we treat recursive-edits as if they were run in a sort > of separate thread (with the original thread blocked until the new > thread exits)? I don't think we can do that by default. We need some evidence that this is the intent. > I think we can't do that in general, since I think we sometimes do want > let-bindings performed around `read-from-minibuffer` to affect the > command executed inside the minibuffer. Exactly. And doing so is a very wide-spread paradigm in Emacs. Which is one reason why enable-recursive-minibuffers is not turned on by default, and should be considered an advanced feature for users who "know what they are doing" and are ready to sustain the consequences. > But we should maybe experiment with it to get a clearer idea of > where we do want/need it and where we don't. Perhaps. But I'd like to hear concrete ideas for such experiments before I have an opinion on their value.