From: Drew Adams <drew.adams@oracle.com>
To: Mark Oteiza <mvoteiza@udel.edu>, 25151@debbugs.gnu.org
Subject: bug#25151: 26.0.50; read-char prompt does not minibuffer face
Date: Fri, 9 Dec 2016 13:09:58 -0800 (PST) [thread overview]
Message-ID: <a98de764-0489-4dee-8086-348729d94d99@default> (raw)
In-Reply-To: <87vautey8k.fsf@udel.edu>
This raises a good question.
I guess you are suggesting that face `minibuffer-prompt'
should be used here? If so, is that face intended to be a
prompt face in general (i.e., THE prompt face, by default)
or just a _minibuffer_ prompt face?
It might make sense for the faces for other kinds of prompt
to look the same, by default, as `minibuffer-prompt'. (Or
it might not.)
But according to its name, face `minibuffer-prompt' is
specific to prompting when reading input in the minibuffer.
(And that's not the case for `read-char', `y-or-n-p', etc.)
It could be decided that `minibuffer-prompt' is to be used
for prompting in general. In that case it really should be
called something like `prompt'.
But I think it would make more sense to create a separate
face `prompt', and (perhaps) let `minibuffer-prompt' inherit
from it.
Some users might, in particular, want to see a difference
when they are prompted and reading is NOT from the minibuffer.
Functions that read characters without using the minibuffer
can confuse users, and a difference in prompt face could give
them an idea that input is being read differently.
Recently Emacs Dev decided to just add face `minibuffer-prompt'
to the prompt for `y-or-n-p'. I'd sooner see a separate face
be used for non-minibuffer input prompting (even if the default
appearance might be the same).
next prev parent reply other threads:[~2016-12-09 21:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 18:47 bug#25151: 26.0.50; read-char prompt does not minibuffer face Mark Oteiza
2016-12-09 21:09 ` Drew Adams [this message]
2021-02-06 11:44 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a98de764-0489-4dee-8086-348729d94d99@default \
--to=drew.adams@oracle.com \
--cc=25151@debbugs.gnu.org \
--cc=mvoteiza@udel.edu \
/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.