From: Stefan Kangas <stefan@marxist.se>
To: Drew Adams <drew.adams@oracle.com>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: "40750@debbugs.gnu.org" <40750@debbugs.gnu.org>,
ndame <ndame@protonmail.com>
Subject: bug#40750: [External] : bug#40750: Use error face for errors
Date: Sat, 25 Sep 2021 09:59:17 -0700 [thread overview]
Message-ID: <CADwFkmmFd20y9qCuq=7iRxEnRhYj2E5sMhK2vypJjcLnBkGzwA@mail.gmail.com> (raw)
In-Reply-To: <SJ0PR10MB5488CD0C3DF615CFF84D751DF3A59@SJ0PR10MB5488.namprd10.prod.outlook.com>
Drew Adams <drew.adams@oracle.com> writes:
> Add a user option, defaulting to no change from
> the traditional behavior, which causes error and
> warning messages to preserve text properties on
> the strings they use.
That's not what happens, see Bug#50785.
> Code should be able to control the appearance
> of text it uses when interacting with users.
> And users should be able to override this or
> (better) configure it.
Having a face is exactly the way to give users control over what this
looks like.
Of course, the error face should not just remove any faces that are
already there; that precludes making e.g. keybindings stand out with the
`help-key-binding' face. So you would need to give the error-message
face lower priority.
next prev parent reply other threads:[~2021-09-25 16:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 18:54 bug#40750: Use error face for errors ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-21 16:06 ` Lars Ingebrigtsen
2021-01-21 17:35 ` Basil L. Contovounesios
2021-01-21 17:38 ` Lars Ingebrigtsen
2021-09-25 2:41 ` Stefan Kangas
2021-09-25 2:42 ` Lars Ingebrigtsen
2021-09-25 15:46 ` bug#40750: [External] : " Drew Adams
2021-09-25 16:59 ` Stefan Kangas [this message]
2022-05-23 11:55 ` Lars Ingebrigtsen
2021-11-02 6:31 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='CADwFkmmFd20y9qCuq=7iRxEnRhYj2E5sMhK2vypJjcLnBkGzwA@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=40750@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.org \
--cc=ndame@protonmail.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).