From: Richard Stallman <rms@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 46583@debbugs.gnu.org
Subject: bug#46583: 28.0.50; nested minibuffers
Date: Fri, 19 Feb 2021 00:41:34 -0500 [thread overview]
Message-ID: <E1lCyXm-0004Nt-Cl@fencepost.gnu.org> (raw)
In-Reply-To: <87v9aqil93.fsf@mail.linkov.net> (message from Juri Linkov on Wed, 17 Feb 2021 20:48:08 +0200)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> The problem is that currently it's impossible for a command
> to override enable-recursive-minibuffers only for its own use,
> while keeping it disabled for more recursive minibuffer calls.
I see. Thanks.
> Maybe enable-recursive-minibuffers should support a numeric value
> that is decremented in every recursive minibuffer calls
> until reaching zero value that disables more recursive calls?
That should be a simple and adequate fix.
I don't see a need to support values greater than 1,
but I don't think they do any harm, and I see
no way to make this simpler by not supporting them.
--
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2021-02-19 5:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 4:03 bug#46583: 28.0.50; nested minibuffers Richard Stallman
2021-02-17 18:48 ` Juri Linkov
2021-02-17 19:46 ` Eli Zaretskii
2021-02-17 20:20 ` Juri Linkov
2021-02-17 20:35 ` Eli Zaretskii
2021-02-18 9:39 ` Juri Linkov
2021-02-18 14:31 ` Eli Zaretskii
2021-02-18 17:17 ` Juri Linkov
2021-02-19 5:41 ` Richard Stallman [this message]
2022-06-17 15:23 ` Lars Ingebrigtsen
2022-06-17 19:20 ` Juri Linkov
2022-06-18 11:33 ` Lars Ingebrigtsen
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=E1lCyXm-0004Nt-Cl@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=46583@debbugs.gnu.org \
--cc=juri@linkov.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).