From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 1375@debbugs.gnu.org
Subject: bug#1375: 23.0.60; Elisp manual node Special Properties
Date: Thu, 07 Jul 2011 22:39:11 +0200 [thread overview]
Message-ID: <m3hb6xomfk.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <000001c94a13$d4734d10$0200a8c0@us.oracle.com> (Drew Adams's message of "Tue, 18 Nov 2008 22:55:37 -0800")
"Drew Adams" <drew.adams@oracle.com> writes:
>
> In the simplest case, the value is a face name. It can also be a
> list; then each element can be any of these possibilities;
>
> * A face name (a symbol or string).
>
> * A property list of face attributes. This has the form
> (KEYWORD VALUE ...), where each KEYWORD is a face attribute
> name and VALUE is a meaningful value for that attribute.
> With this feature, you do not need to create a face each time
> you want to specify a particular attribute for certain text.
> *Note Face Attributes::.
>
> * A cons cell with the form `(foreground-color . COLOR-NAME)'
> or `(background-color . COLOR-NAME)'. These are older,
> deprecated equivalents for `(:foreground COLOR-NAME)' and
> `(:background COLOR-NAME)'. Please convert code that uses
> them.
>
> It works to use the latter two forms directly as the value of the
> `face' property.
>
> The "latter two forms" in the last sentence seems to refer to the last
> two bullets. Is that right? And the first sentence above seems to
> refer to the first bullet, no?
Yes, that's not very clear.
The documentation has changed in the mean time -- the third item has
been dropped. But it still remained less clear than it could have been,
so I've rewritten it slightly now.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
prev parent reply other threads:[~2011-07-07 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 6:55 bug#1375: 23.0.60; Elisp manual node Special Properties Drew Adams
2011-07-07 20:39 ` Lars Magne Ingebrigtsen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3hb6xomfk.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=1375@debbugs.gnu.org \
--cc=drew.adams@oracle.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.