From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Must prevent switching from recursive edit buffers
Date: Sat, 21 Dec 2024 10:22:31 -0500 [thread overview]
Message-ID: <jwvttaxf4u0.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <Z2QUVayAX8Ql8RCH@lco2> (Jean Louis's message of "Thu, 19 Dec 2024 15:40:53 +0300")
> 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
next prev parent reply other threads:[~2024-12-21 15:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 7:50 Must prevent switching from recursive edit buffers Jean Louis
2024-12-18 16:13 ` [External] : " Drew Adams
2024-12-18 23:41 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-12-19 12:40 ` Jean Louis
2024-12-21 15:22 ` Stefan Monnier [this message]
2024-12-21 17:38 ` Jean Louis
2024-12-21 18:08 ` Stefan Monnier
2024-12-21 18:53 ` [External] : " Drew Adams
2024-12-21 19:33 ` Jean Louis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvttaxf4u0.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).