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 13:08:31 -0500 [thread overview]
Message-ID: <jwvldw8ex04.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <Z2b9DOw6v3Go-fLK@lco2> (Jean Louis's message of "Sat, 21 Dec 2024 20:38:20 +0300")
>> Kinds would be things like `minibuffer`, `debugger`, `edebug`,
>> `query-replace`, ...
>
> But in my work they have always names. My recursive buffer opens full
> screen like any other.
That's a completely different problem since it's not about
recursive-edit in general but about those specific recursive-edits
introduced by your specific function, so you have complete freedom to
solve the problem on your side.
E.g. your function could add those buffers to a list of
`my-read-from-buffers` which you can then display via an ad-hoc command
you could implement, or you could display them in your modeline, or ...
> - sometimes I have deleted it and [[[[]]]] still remain on the
> modeline; and I have no idea why;
Deleting a buffer won't get you out of the recursive edit (you didn't
tell Emacs about the link between the buffer and the recursive-edit;
you need a `kill-buffer-hook` for that).
Also, you can only get out of the most recent recursive-edit.
So, you can't eliminate the Nth recursive edit without also eliminating
all the >Nth recursive-edits.
Stefan
next prev parent reply other threads:[~2024-12-21 18:08 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
2024-12-21 17:38 ` Jean Louis
2024-12-21 18:08 ` Stefan Monnier [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvldw8ex04.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.