From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 19368@debbugs.gnu.org
Subject: bug#19368: 25.0.50; NSM prompt is not self-explanatory enough
Date: Fri, 05 Feb 2016 14:35:13 +1100 [thread overview]
Message-ID: <871t8rx21a.fsf@gnus.org> (raw)
In-Reply-To: <83bnn762d6.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 13 Dec 2014 16:39:01 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> To reproduce:
>
> emacs -Q
> M-x eww RET www.google.com RET
> Click on the "Sign in" link
>
> The NSM shows a buffer with description of why it failed to verify the
> certificate of accounts.google.com, and prompts in the minibuffer like
> this:
>
> Continue connecting? (No, Session only, Always)
>
> It expects me to press either N, S, or A, but that is not clear enough
> from the prompt.
>
> I suggest to change the prompt to something like this:
>
> Continue connecting? ([N]o, [S]ession only, [A]lways)
>
> Alternatively, the first letter could be underlined (assuming we can
> rely on every supported terminal to be able to display underlined
> characters).
This has now been fixed, and it's using read-multiple-choice, which
makes the character choices underline and bold on graphical systems, and
"[l]ike this" on non-graphical ones.
Some terminals do have the capability to underline and bold stuff, but
have nil (display-graphic-p), right? Is there a way to determine
whether we're running on one of those terminals? Because
underlining/bolding is prettier than [t]his.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-02-05 3:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87a8j3llba.fsf@lifelogs.com>
2014-12-13 14:39 ` bug#19368: 25.0.50; NSM prompt is not self-explanatory enough Eli Zaretskii
2014-12-14 4:43 ` Stefan Monnier
2014-12-14 11:37 ` Ted Zlatanov
2016-02-05 3:43 ` Lars Ingebrigtsen
2014-12-14 8:12 ` Lars Magne Ingebrigtsen
2014-12-14 16:02 ` Eli Zaretskii
2014-12-14 22:48 ` Stefan Monnier
2014-12-21 11:50 ` Lars Ingebrigtsen
2016-02-04 7:24 ` Lars Ingebrigtsen
2016-02-04 16:47 ` Eli Zaretskii
2016-02-05 3:53 ` Lars Ingebrigtsen
2016-02-05 3:35 ` Lars Ingebrigtsen [this message]
2016-02-05 7:42 ` Eli Zaretskii
2016-02-05 7:46 ` Lars Ingebrigtsen
2016-02-05 9:34 ` Eli Zaretskii
2016-02-06 3:09 ` Lars Ingebrigtsen
2016-06-02 14:31 ` Archived problem report bug#19368 (bug#19368: 25.0.50; NSM prompt is not self-explanatory enough) GNU bug Tracking System
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=871t8rx21a.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=19368@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 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).