From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "62146@debbugs.gnu.org" <62146@debbugs.gnu.org>
Subject: bug#62146: 26.3; Allow users to get help on y/n prompt
Date: Sun, 12 Mar 2023 18:18:15 +0000 [thread overview]
Message-ID: <SJ0PR10MB54888E573620F109B12BFB3AF3B89@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83r0ttub4i.fsf@gnu.org>
> > Please consider allowing a help character, such as `?' or `C-h', to
> > give users more info about y/n prompting - info that might help with this
> > user's confusion (maybe some info such as that offered by NickD's
> > answer).
>
> The help info is right above the prompt.
>
> And I don't really understand what that user wanted to do, and why he
> tried doing that when prompted for a y/n response.
>
> > Consider, in particular, the context of hitting a key for a disabled
> > command (the OP's context), and seeing the Help text for dealing with
> > disabled commands, including a link that is impossible to access while
> > in the y/n read.
>
> To cancel type 'n' -- this text is right in the face of the user.
I'm guessing it might help to make clear that `n'
will hide buffer *Disabled Command*, but it's not
killed and you can get back to it (e.g. to read it
again, follow the link, or whatever) using `C-x b'.
Another aid might be to not hide *Disabled Command*.
Another aid might be to also point/link to (emacs)
`Disabling', for more information about disabled
commands. `i disabled command' takes you to that
node, and although the info there is mostly about
disabling (and enabling disabled) commands, it
also explains what a disabled command means etc.
I think the general point is that (1) showing
text that links somewhere, while not letting you
follow the link and (2) hiding that text if you
use `n' (or anything else), introduces unnecessary
confusion.
It's a bit as if the y/n dialog were ignorant of
the text being shown. That text can invite a
quest for more info, but the simple y/n dialog
prevents that. I can understand why/how a user
might think/say "Wtf?"
You may disagree that this dialog/info could or
should be improved, of course.
prev parent reply other threads:[~2023-03-12 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 16:18 bug#62146: 26.3; Allow users to get help on y/n prompt Drew Adams
2023-03-12 17:34 ` Eli Zaretskii
2023-03-12 18:18 ` Drew Adams [this message]
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=SJ0PR10MB54888E573620F109B12BFB3AF3B89@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=62146@debbugs.gnu.org \
--cc=eliz@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.