From: Stephen Berman via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 72389@debbugs.gnu.org, rms@gnu.org, Dan Jacobson <jidanni@jidanni.org>
Subject: bug#72389: Unfair prompts and documentation of Emergency Escape
Date: Sun, 04 Aug 2024 13:23:17 +0200 [thread overview]
Message-ID: <877ccwv8ey.fsf@gmx.net> (raw)
In-Reply-To: <865xsgsh53.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 04 Aug 2024 13:43:04 +0300")
On Sun, 04 Aug 2024 13:43:04 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Dan Jacobson <jidanni@jidanni.org>
>> Cc: 72389@debbugs.gnu.org, rms@gnu.org
>> Date: Sun, 04 Aug 2024 18:36:57 +0800
>>
>> >> Emacs is resuming after an emergency escape.
>> >> Auto-save? (y or n)
>> Say: Auto-save? (y or n, RET)
>>
>> >> Abort (and dump core)? (y or n)
>> Say: Abort (and dump core)? (y or n, RET)
>>
>> Also say that in (info "(emacs) Emergency Escape").
>
> Any key except 'y' will do the same as 'n'. So we have to say
>
> Auto-save? (y or n, RET, a, b, c, d, e, f, ..., A, B, C, D, E, F,...)
>
> Right?
>
> More importantly, this text:
>
> (y or n, RET)
>
> doesn't really say what will RET do.
Instead of asking a question, what about something like this:
Type 'y' to auto-save.
Type 'y' to abort (and dump core).
and perhaps adding something like "(typing any other key does nothing)"
for completeness? Or a similar or more suitable message could be
displayed on typing any other key.
Steve Berman
next prev parent reply other threads:[~2024-08-04 11:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 1:17 bug#72389: Unfair prompts and documentation of Emergency Escape Dan Jacobson
2024-07-31 13:51 ` Eli Zaretskii
2024-08-04 10:36 ` Dan Jacobson
2024-08-04 10:43 ` Eli Zaretskii
2024-08-04 11:23 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-08-04 11:43 ` Eli Zaretskii
2024-08-04 14:04 ` Dan Jacobson
2024-08-04 14:17 ` Eli Zaretskii
2024-08-16 13:42 ` bug#72389: So easy to trigger Dan Jacobson
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=877ccwv8ey.fsf@gmx.net \
--to=bug-gnu-emacs@gnu.org \
--cc=72389@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jidanni@jidanni.org \
--cc=rms@gnu.org \
--cc=stephen.berman@gmx.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).