From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, 46583@debbugs.gnu.org
Subject: bug#46583: 28.0.50; nested minibuffers
Date: Wed, 17 Feb 2021 22:20:01 +0200 [thread overview]
Message-ID: <87v9aqe9am.fsf@mail.linkov.net> (raw)
In-Reply-To: <83zh025vg8.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 17 Feb 2021 21:46:15 +0200")
>> Let-binding enable-recursive-minibuffers temporarily to t was necessary
>> to fix bug#17272/bug#19064.
>>
>> So when the minibuffer is already activated, and a minibuffer command
>> wants to ask a question, displaying another recursive minibuffer with
>> such question should override the value of enable-recursive-minibuffers.
>
> Those bugs are about an echo-area message overwriting the minibuffer
> prompt, are they not? If so, doesn't the set-message-function feature
> we now have fixed those bugs indirectly, this removing the need for
> let-binding enable-recursive-minibuffers?
This problem is not fixed by set-message-function that only improves
messaging. The problem was reported by João in the same bug report
https://debbugs.gnu.org/17272#114
Emacs -Q
M-x fido-mode
C-x b
C-k ;; to kill the Messages buffer
This affects yes-or-no-p that C-k needs to use from the minibuffer
in fido-mode.
next prev parent reply other threads:[~2021-02-17 20:20 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 [this message]
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
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=87v9aqe9am.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=46583@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rms@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 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).