unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dave Love <fx@gnu.org>
To: Jason Rumney <jasonr@gnu.org>
Cc: bug-gnu-emacs@gnu.org, jidanni@jidanni.org
Subject: Re: assuming light or dark background
Date: Fri, 22 Feb 2008 17:19:34 +0000	[thread overview]
Message-ID: <87lk5c29jt.fsf@liv.ac.uk> (raw)
In-Reply-To: 47ABC40D.4030302@gnu.org

Jason Rumney <jasonr@gnu.org> writes:

> jidanni@jidanni.org wrote:
>> RFCs are unreadable now for me. Must be due to
>>
>>   (defface rfcview-headlink-face
>>     '((t (:foreground "blue"))
>>       (t (:bold t)))
>>     "Face used for hyperlinks to headings."
>>     :group 'rfcview)
>>
>
> This doesn't appear to be part of Emacs.

Indeed.  It isn't part of
<URL:http://www.loveshack.ukfsn.org/emacs/rfcview.el> either.

> Probably a better way of
> defining that face is
>
> (defface rfcview-headlink-face
>    '((t (:inherit 'link)))
>    "Face used for hyperlinks to headngs."
>    :group 'rfcview)

(facep 'link)
  => nil

> That way it will take advantage of any variations that already exist
> for the built-in link face, such as light, dark, grayscale, or user
> customizations.

If there was a face defined for hyperlinks in the relevant versions of
Emacs, it would be appropriate just to use it (with the `face' custom
type), not define more vanity faces.  That was what we intended for
Emacs 21 as far as I remember, even if it didn't get done well.  I
shouldn't have 281 separately-defined faces in my current session --
Gnus being the biggest culprit.




  reply	other threads:[~2008-02-22 17:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-07 23:45 assuming light or dark background jidanni
2008-02-08  2:53 ` Jason Rumney
2008-02-22 17:19   ` Dave Love [this message]
2008-02-23  0:41     ` jidanni

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=87lk5c29jt.fsf@liv.ac.uk \
    --to=fx@gnu.org \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=jasonr@gnu.org \
    --cc=jidanni@jidanni.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).