From: Juri Linkov <juri@jurta.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: font-lock-warning-face
Date: Fri, 24 Feb 2006 02:27:38 +0200 [thread overview]
Message-ID: <87hd6pr1gx.fsf@jurta.org> (raw)
In-Reply-To: <17402.61774.37409.530598@kahikatea.snap.net.nz> (Nick Roberts's message of "Tue, 21 Feb 2006 23:54:06 +1300")
> > Maybe, but we would need to think about this somewhat more before
> > doing it. What other uses would we want this to be used for?
>
> Well I don't know how many you want, but additionally:
>
> 1) The face dired-marked inherits from it.
> 2) The face ido-incomplete-regexp inherits from it.
> 3) The face iswitchb-invalid-regexp inherits from it.
> 4) The face cvs-fi-conflict-face is an alias for it.
> 5) The face compilation-error inherits from it.
dired-marked is font-lock based face (used in `dired-font-lock-keywords').
compilation-error is indirectly font-lock based face as well (used via
`compilation-mode-font-lock-keywords'). So I think for these faces it is
appropriate to inherit from font-lock-warning-face. Other faces have
nothing to do with font-lock-warning-face, so inheriting from a new face
`warning' would be good for easy customization.
--
Juri Linkov
http://www.jurta.org/emacs/
prev parent reply other threads:[~2006-02-24 0:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 11:38 font-lock-warning-face Nick Roberts
2006-02-18 23:35 ` font-lock-warning-face Dan Nicolaescu
2006-02-19 0:38 ` font-lock-warning-face Nick Roberts
2006-02-19 17:45 ` font-lock-warning-face Richard M. Stallman
2006-02-21 10:54 ` font-lock-warning-face Nick Roberts
2006-02-22 3:35 ` font-lock-warning-face Miles Bader
2006-02-22 21:01 ` font-lock-warning-face Nick Roberts
2006-02-24 19:41 ` font-lock-warning-face Richard Stallman
2006-02-24 23:28 ` font-lock-warning-face Juri Linkov
2006-02-26 12:10 ` font-lock-warning-face Richard Stallman
2006-02-24 0:28 ` font-lock-warning-face Juri Linkov
2006-02-24 0:27 ` Juri Linkov [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=87hd6pr1gx.fsf@jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.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).