From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: rms@gnu.org, 46583@debbugs.gnu.org
Subject: bug#46583: 28.0.50; nested minibuffers
Date: Thu, 18 Feb 2021 16:31:31 +0200 [thread overview]
Message-ID: <83im6p5tx8.fsf@gnu.org> (raw)
In-Reply-To: <87a6s1n1rx.fsf@mail.linkov.net> (message from Juri Linkov on Thu, 18 Feb 2021 11:39:54 +0200)
> From: Juri Linkov <juri@linkov.net>
> Cc: rms@gnu.org, 46583@debbugs.gnu.org
> Date: Thu, 18 Feb 2021 11:39:54 +0200
>
> > It prevents messages from overwriting minibuffer prompts. And both of
> > the bugs you mentioned seem to be about messages that overwrite such
> > prompts. So what am I missing?
>
> Sorry for mentioning old bugs that added confusion to this bug report.
> What we have now is a new bug found by Richard:
>
> I save a file that is read-only, so I am asked
>
> File phones is write-protected; try to save anyway? (yes or no)
>
> Then I type C-x b and it tries to read a buffer name.
>
> I could send a patch that fixes this bug.
Thanks. I hoped first to understand why we bind
enable-recursive-minibuffers in these cases, but if you prefer to
begin with a patch, please do, and let's take it from there.
next prev parent reply other threads:[~2021-02-18 14:31 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 [this message]
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=83im6p5tx8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46583@debbugs.gnu.org \
--cc=juri@linkov.net \
--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).