From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.help Subject: Re: Must prevent switching from recursive edit buffers Date: Sat, 21 Dec 2024 10:22:31 -0500 Message-ID: References: <2756a07624cab7ceb1c68dd24e671ef7.support1@rcdrun.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33647"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Sat Dec 21 16:23:18 2024 Return-path: Envelope-to: geh-help-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 ) id 1tP1K2-0008aq-Ia for geh-help-gnu-emacs@m.gmane-mx.org; Sat, 21 Dec 2024 16:23:18 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tP1JU-0003md-1b; Sat, 21 Dec 2024 10:22: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 ) id 1tP1JS-0003mT-8V for help-gnu-emacs@gnu.org; Sat, 21 Dec 2024 10:22:42 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tP1JO-0003r3-A0 for help-gnu-emacs@gnu.org; Sat, 21 Dec 2024 10:22:41 -0500 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 8E3C1100055; Sat, 21 Dec 2024 10:22:33 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1734794553; bh=U9Iaw1i1wv4vyrKut/t+8pH2wX8ki5pPC1xvYWMvADU=; h=From:To:Subject:In-Reply-To:References:Date:From; b=jpa+Y7Dc/cAA3ioT++MEO7Xa2KxtXlFfpjc20ea7kD8C45xbGqZYn3z+GBHeIS4Lv JAKTgwM7DSvmwZdTCKFCRqhAX3uZX9Gk1udX0HQAmfRPyPGkP1NUneXLDjJ/TpGs9i V6H0G0h9Qq1Iqv9LZvq13CrobmDN7gXIaAlL16LcQmiSLEVXvGH+iVxUeijaoH3VsB V11wgLm9IDef9q+x3VsRtkA3qPX+k76J+n/AEqdLGLzUaGHzuusggt9NXba9TYnEDj XOi4epL8QAZn75OajBan8bgE5ZYthGJoOB1Funf6ofkN2wAmXTfHBDK5l9x/AG7wek 7kAGDX9dqmJUg== Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id EAB97100043; Sat, 21 Dec 2024 10:22:32 -0500 (EST) Original-Received: from asado (unknown [199.119.74.1]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id C0F4E120384; Sat, 21 Dec 2024 10:22:32 -0500 (EST) In-Reply-To: (Jean Louis's message of "Thu, 19 Dec 2024 15:40:53 +0300") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.help:148906 Archived-At: > That is some mystery. Those recursive-edit buffers show as > > [[[[[(Mail WK Fill)]]]]] > > but I cannot know in the list of buffer and CANNOT SEE to what buffers > those [[[[]]]] belogns. Hmm... currently I think that Emacs's code does not record a clear association between a recursive edit and "the buffer to which it belongs" (arguably even this concept is ill-defined, although in practice it is probably true that there is almost always a buffer with which we can associate the recursive edit). Maybe we could start by implementing a command which shows a list of current recursive edits by walking the backtrace and trying to guess which "kind" of recursive edit it is and to which buffer is "belongs". Kinds would be things like `minibuffer`, `debugger`, `edebug`, `query-replace`, ... That would have to rely on ad-hoc rules, but that would give us some experience from which we could hopefully design a better API which ELisp packages which use `recursive-edit` can then use to provide that same information more directly. Stefan