From: Simon Josefsson <jas@extundo.com>
Subject: Re: defface/defcustom question
Date: Sat, 09 Aug 2003 03:54:30 +0200 [thread overview]
Message-ID: <ilu8yq3ppd5.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3znijpzhu.fsf@defun.localdomain> (Jesper Harder's message of "Sat, 09 Aug 2003 00:15:41 +0200")
Jesper Harder <harder@myrealbox.com> writes:
> In some places Gnus faces are defined both with `defface' _and_
> `defcustom'. E.g.
>
> ,----
> | (defface gnus-server-opened-face
> | '((((class color) (background light)) (:foreground "Green3" :bold t))
> | (((class color) (background dark)) (:foreground "Green1" :bold t))
> | (t (:bold t)))
> | "Face used for displaying OPENED servers"
> | :group 'gnus-server-visual)
> |
> | [...]
> |
> | (defcustom gnus-server-opened-face 'gnus-server-opened-face
> | "Face name to use on OPENED servers."
> | :group 'gnus-server-visual
> | :type 'face)
> `----
>
> This means that the face shows up twice when you use Customize. It
> looks like a mistake to me ... or is there a reason for doing it?
Aren't variables and faces different things? The variable identifies
the name of the face to use, and the face define the actual face. An
extra indirection. Compare the ':type face' documentation:
`face'
The value must be a symbol which is a face name, and you can do
completion with `M-<TAB>'.
next prev parent reply other threads:[~2003-08-09 1:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-08 22:15 Jesper Harder
2003-08-09 1:54 ` Simon Josefsson [this message]
2003-08-09 9:55 ` Kai Großjohann
2003-08-09 11:32 ` Simon Josefsson
2003-08-09 13:13 ` Kai Großjohann
2003-08-09 15:45 ` Simon Josefsson
2003-08-09 16:43 ` Jesper Harder
2003-08-09 17:16 ` Alan Shutko
2003-08-09 18:05 ` Simon Josefsson
2003-08-09 18:44 ` Alan Shutko
2003-08-10 20:34 ` Kai Großjohann
2003-08-25 14:41 ` Per Abrahamsen
2003-08-10 20:33 ` Kai Großjohann
2003-08-12 11:53 ` Simon Josefsson
2003-08-14 21:23 ` Kai Großjohann
2003-08-15 12:07 ` Alex Schroeder
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ilu8yq3ppd5.fsf@latte.josefsson.org \
--to=jas@extundo.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.
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 NNTP newsgroup(s).