From: martin rudalics <rudalics@gmx.at>
To: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: dired-warning
Date: Fri, 12 Oct 2007 09:06:27 +0200 [thread overview]
Message-ID: <470F1CF3.6050101@gmx.at> (raw)
In-Reply-To: <87ve9dut5o.fsf_-_@jurta.org>
> Since this change was synced to the trunk and I see it in action now,
> I agree it was a bad idea.
The problem provoking that change was that with eight colors
`font-lock-comment-delimiter-face' usurpated `font-lock-comment-face'
leaving the latter without foreground.
> I propose to add a new face font-lock-error-face, to copy its definition
> from font-lock-warning-face, and to copy the definition of compilation-warning
> to font-lock-warning-face. So dired-warning inheriting now from
> font-lock-warning-face will use the new definition.
>
> Making this distinction between two faces font-lock-error-face and
> font-lock-warning-face will be useful for other packages where
> error text should be displayed in the strong color, and warnings in
> more subdued color.
Would this fit into an eight colors scheme?
> PS: This proposal is for the trunk. For Emacs-22 I think we should
> restore the old color by copying definitions of font-lock-comment-face
> and font-lock-comment-delimiter-face to dired-warning like:
>
> (defface dired-warning
> '((((class color) (min-colors 88) (background light))
> (:foreground "Firebrick"))
> (((class color) (min-colors 88) (background dark))
> (:foreground "chocolate1"))
> (((class color) (min-colors 8) (background light))
> :foreground "red")
> (((class color) (min-colors 8) (background dark))
> :foreground "red1"))
> "Face used to highlight a part of a buffer that needs user attention."
> :group 'dired-faces
> :version "22.1")
dired.el face specs are based on inheriting, hence this might break some
people's customizations.
next prev parent reply other threads:[~2007-10-12 7:06 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 9:32 bug of display-table & make-glyph-code levin
2007-09-04 16:45 ` Richard Stallman
2007-09-04 18:09 ` martin rudalics
2007-09-04 19:08 ` Glenn Morris
2007-09-05 5:58 ` levin
2007-09-05 7:22 ` Glenn Morris
2007-09-05 8:22 ` Du Jingwu
2007-09-05 20:02 ` Richard Stallman
2007-09-05 6:16 ` Richard Stallman
2007-09-05 7:21 ` Glenn Morris
2007-09-05 8:08 ` martin rudalics
2007-09-05 8:37 ` Glenn Morris
2007-09-05 9:58 ` martin rudalics
2007-09-05 16:44 ` Glenn Morris
2007-09-05 17:34 ` martin rudalics
2007-09-06 5:29 ` Glenn Morris
2007-09-06 8:49 ` martin rudalics
2007-09-07 1:44 ` Glenn Morris
2007-09-07 8:02 ` martin rudalics
2007-09-07 17:48 ` Glenn Morris
2007-09-08 8:52 ` martin rudalics
2007-09-08 7:00 ` Richard Stallman
2007-09-12 7:37 ` Glenn Morris
2007-09-12 8:28 ` martin rudalics
2007-10-11 23:57 ` dired-warning (was: bug of display-table & make-glyph-code) Juri Linkov
2007-10-12 7:06 ` martin rudalics [this message]
2007-10-14 21:21 ` dired-warning Juri Linkov
2007-09-05 17:54 ` bug of display-table & make-glyph-code Eli Zaretskii
2007-09-05 8:51 ` levin
2007-09-06 4:59 ` Richard Stallman
2007-09-05 10:08 ` frame resizing under KDE (was Re: bug of display-table & make-glyph-code) Stephen Berman
2007-09-05 17:42 ` martin rudalics
2007-09-06 6:17 ` frame resizing under KDE (was Re: bug of display-table & make-glyph-code ) Levin
2007-09-06 12:01 ` frame resizing under KDE Stephen Berman
2007-09-06 1:15 ` bug of display-table & make-glyph-code Chong Yidong
2007-09-06 9:09 ` martin rudalics
2007-09-06 14:08 ` Stefan Monnier
2007-09-06 14:49 ` martin rudalics
2007-09-06 20:34 ` Stefan Monnier
2007-09-06 21:08 ` martin rudalics
2007-09-07 17:45 ` Stefan Monnier
2007-09-07 18:30 ` martin rudalics
2007-09-07 20:25 ` Stefan Monnier
2007-09-08 9:22 ` display-buffer-change (was Re: bug of display-table & make-glyph-code) martin rudalics
2007-09-09 19:33 ` display-buffer-change Stefan Monnier
2007-09-09 21:42 ` display-buffer-change martin rudalics
2007-09-10 6:57 ` display-buffer-change David Kågedal
2007-09-10 8:31 ` display-buffer-change martin rudalics
2007-09-10 6:48 ` display-buffer-change David Kågedal
2007-09-10 8:00 ` display-buffer-change martin rudalics
2007-09-07 6:32 ` bug of display-table & make-glyph-code Richard Stallman
2007-09-06 5:00 ` Richard Stallman
2007-09-06 5:27 ` Glenn Morris
2007-09-05 9:15 ` Kim F. Storm
2007-09-05 17:38 ` martin rudalics
2007-09-05 20:43 ` Kim F. Storm
2007-09-07 5:11 ` Kenichi Handa
2007-09-07 8:47 ` Eli Zaretskii
2007-09-07 12:25 ` Kenichi Handa
2007-09-07 18:37 ` Eli Zaretskii
2007-09-08 7:00 ` Richard Stallman
2007-09-10 2:43 ` Kenichi Handa
2007-09-10 3:18 ` Eli Zaretskii
2007-09-07 19:53 ` Richard Stallman
2007-09-10 1:12 ` Richard Stallman
2007-09-10 4:15 ` Kenichi Handa
2007-09-10 5:50 ` Stefan Monnier
2007-09-10 6:29 ` Kenichi Handa
2007-09-10 11:51 ` Kim F. Storm
2007-09-10 14:20 ` Leo
2007-09-11 12:49 ` Stefan Monnier
2007-09-11 20:30 ` Richard Stallman
2007-09-11 21:50 ` Kim F. Storm
2007-09-10 19:40 ` Eli Zaretskii
2007-09-11 0:28 ` Kenichi Handa
2007-09-12 8:45 ` Richard Stallman
2007-09-11 20:31 ` Richard Stallman
2007-09-12 6:55 ` Eli Zaretskii
2007-09-13 16:30 ` Richard Stallman
2007-09-10 23:54 ` Richard Stallman
2007-09-11 0:09 ` Drew Adams
2007-09-11 0:33 ` Kenichi Handa
2007-09-11 1:24 ` Drew Adams
2007-09-06 5:00 ` Richard Stallman
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=470F1CF3.6050101@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.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).