unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: ndame via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "40750@debbugs.gnu.org" <40750@debbugs.gnu.org>
Subject: bug#40750: Use error face for errors
Date: Tue, 02 Nov 2021 06:31:23 +0000	[thread overview]
Message-ID: <391z1J-mBPJMY63PRs2P2AIJhHbIfBAvtHQXLqvwn2UehzpH1Sevqv4tHmiEx_WF7VvjrFFQ8cyy8WbmjLRtCCIcd3a-M1YoFBNXcRhbYiw=@protonmail.com> (raw)
In-Reply-To: <O06ygzDk4H-HZOIABHC2itMNG-FV2ZkSYnT8xJdGQ-jSv79LMM0NA1m4N_zst9rdoXo0Q-vDmHaEQCuZ4raF3uxwCI2_jHaP55EJOMzLAzE=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 472 bytes --]

> I think having Emacs using red for error message in the echo area etc would look pretty odd? Anybody got an opinion here?

I don't think it looks odd, it just makes errors more conspicuous which is not a bad thing:

(run-with-idle-timer
0 nil
(lambda ()
(message (propertize "Error in post-command-hook (my-test-post-command): (args-out-of-range 0 1)"
'face 'error))))

But it can have its own face (error-message) to use by error and signal, so people can customize it.

[-- Attachment #2: Type: text/html, Size: 801 bytes --]

      parent reply	other threads:[~2021-11-02  6:31 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
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 [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

  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='391z1J-mBPJMY63PRs2P2AIJhHbIfBAvtHQXLqvwn2UehzpH1Sevqv4tHmiEx_WF7VvjrFFQ8cyy8WbmjLRtCCIcd3a-M1YoFBNXcRhbYiw=@protonmail.com' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=40750@debbugs.gnu.org \
    --cc=laszlomail@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).