From: Raffaele Ricciardi <rfflrccrd@gmail.com>
To: Drew Adams <drew.adams@oracle.com>, 21112@debbugs.gnu.org
Subject: bug#21112: 25; Patch: show minibuffer messages with a face
Date: Wed, 22 Jul 2015 17:27:47 +0200 [thread overview]
Message-ID: <55AFB673.1030703@gmail.com> (raw)
In-Reply-To: <0628db88-9d3c-41ad-8084-6bd33c32a01f@default>
On 22/07/15 15:44, Drew Adams wrote:
> I haven't looked at the patch, and I misread the request as applying
> to `message' output, not `minibuffer-message'. But I have the same
> response in the latter case - leave it alone, so users can do with
> it what they like.
I understand what you mean and I agree when you say that the current
implementation is more flexible. The problem that this patch tries to
solve is that -- as far as I can see -- all Emacs messages are
currently passed as plain strings, and thus appear in the same face as
user input, making it seem that Emacs is meddling with user input,
which is not the case. Now, requiring callers to specify a face for
every single message would be burdensome, wouldn't it? Maybe, could
we make `minibuffer-message' apply the `minibuffer-prompt' face only
if the message lacks its own faces? Or maybe, could we split
`minibuffer-message' in two functions, one -- internal -- that applies
the `minibuffer-prompt' face and one that doesn't? The same approach
could be applied to the minibuffer prompt, too.
next prev parent reply other threads:[~2015-07-22 15:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 12:46 bug#21112: 25; Patch: show minibuffer messages with a face Raffaele Ricciardi
2015-07-22 13:42 ` Drew Adams
2015-07-22 13:44 ` Drew Adams
2015-07-22 15:27 ` Raffaele Ricciardi [this message]
2015-07-22 15:42 ` Drew Adams
2016-02-23 9:34 ` Lars Ingebrigtsen
2019-06-25 15:50 ` Lars Ingebrigtsen
2019-06-25 19:47 ` Juri Linkov
2019-06-25 20:43 ` Lars Ingebrigtsen
2019-06-26 21:28 ` Juri Linkov
2019-06-27 10:28 ` Lars Ingebrigtsen
2019-06-27 14:22 ` Drew Adams
2019-06-27 20:29 ` Juri Linkov
2019-06-27 21:19 ` Drew Adams
2019-06-27 20:28 ` Juri Linkov
2019-06-27 21:37 ` Drew Adams
2019-07-04 22:01 ` Juri Linkov
2019-06-25 20:54 ` Drew Adams
2019-06-26 21:30 ` Juri Linkov
2019-06-26 22:13 ` Drew Adams
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=55AFB673.1030703@gmail.com \
--to=rfflrccrd@gmail.com \
--cc=21112@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).