all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Jacobson <jidanni@jidanni.org>
To: 72389@debbugs.gnu.org
Subject: bug#72389: Unfair prompts and documentation of Emergency Escape
Date: Wed, 31 Jul 2024 09:17:25 +0800	[thread overview]
Message-ID: <87sevq9x7e.3.fsf@jidanni.org> (raw)

Regarding

   Emacs is resuming after an emergency escape.
   Auto-save? (y or n)
   Abort (and dump core)? (y or n)

and its documentation, (info "(emacs) Emergency Escape"),

well, I would just like to say it is not fair to the user,
to not mention what will happen if they just hit RET.

Not fair in the prompts. Not fair in the documentation.

So the prompts should have one letter bigger, or use [ ] etc.
to indicate if RET=y or if RET=n. And the documentation needs to
document what will happen too.

Or document why it doesn't document it.

Oh, yes, I did try it. Two RETs. Yup.
And I am still alive.
However what did actually happen is a secret.

By the way, maybe a thorough check should be made to identify any other
"test your luck" ambiguous prompts.

Also they need to look different from the prompts that indeed "won't
take RET as an answer" and "demand a real answer, y or n".

emacs-version "29.4"





             reply	other threads:[~2024-07-31  1:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31  1:17 Dan Jacobson [this message]
2024-07-31 13:51 ` bug#72389: Unfair prompts and documentation of Emergency Escape 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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sevq9x7e.3.fsf@jidanni.org \
    --to=jidanni@jidanni.org \
    --cc=72389@debbugs.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.