From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: +face-remapping-20040525-2-c.patch
Date: Thu, 27 May 2004 08:46:58 -0400 [thread overview]
Message-ID: <E1BTKHi-0000BZ-B1@fencepost.gnu.org> (raw)
In-Reply-To: <87r7t8fu5a.fsf@tc-1-100.kawasaki.gol.ne.jp> (message from Miles Bader on Tue, 25 May 2004 23:39:29 +0900)
+ This variable may be be used to locally change the meaning of face-names,
This variable is used for buffer-local changes in the appearance of
a face.
+ for instance making the @code{default} face a variable-pitch face in a
+ particular buffer. It should be
Its value should be
an alist, whose elements have the form
+ @code{(@var{face} @var{remapping@dots{}})};
The @dots should be outside of @var. Only the variable name itself
should be inside @var.
+ Alternate face definitions provided by @code{face-remapping-alist}
+ @emph{replace} the remapped faces, they aren't merged with it.
This is not quite grammatical, and isn't entirely clear.
+ Recursive face-remapping does not result in an error. Instead, if a
+ remapped face is used recursively, the remapping is ignored for the
+ recursive used, and the ``true'' face used instead.
I think I understand what that means, but it isn't easy to translate
into concrete terms. Could you write it more concretely? And give an
example?
+ Because of the previous two properties, an easy way to @emph{add} to a
+ face's definition using @code{face-remapping-alist}, is simply to
+ recursively include the remapped face it the remapped definition (this is
+ not necessary when remapping the @code{default} face, the result will be
+ eventually merged with the true @code{default} by the display mechanism).
Could you give an example?
prev parent reply other threads:[~2004-05-27 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 14:39 +face-remapping-20040525-2-c.patch Miles Bader
2004-05-25 23:22 ` +face-remapping-20040525-2-c.patch Miles Bader
2004-05-27 12:46 ` Richard Stallman [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=E1BTKHi-0000BZ-B1@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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 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.