From: Miles Bader <miles@gnu.org>
Cc: emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: Buffer-local faces
Date: Mon, 3 May 2004 19:19:27 -0400 [thread overview]
Message-ID: <20040503231927.GA9451@fencepost> (raw)
In-Reply-To: <E1BKlnq-0000Lj-6q@fencepost.gnu.org>
On Mon, May 03, 2004 at 06:20:46PM -0400, Richard Stallman wrote:
> Each element is of the form:
> (FACE . NEW-FACE)
> or
> (FACE NEW-FACE MERGE-FACE...),
> which causes NEW-FACE to be used where FACE normally would.
> If present, MERGE-FACE... are merged during display with NEW-FACE.
>
> Wouldn't it be cleaner just to have one kind of element,
> (FACE REPLACEMENT-FACES...)
I think so, but I'm not entirely sure if it's possible; perhaps it is.
The question is whether there are places that want remapping, but don't
operate in terms of face-ids -- e.g., they use `lisp-faces' (lisp vectors),
or face names. Face-ids can represent merged faces, but the other
representations can not, so my original thought while implementing this was
that I'd need to support the concept of a `simple remapping' that merely
returned one face name/vector for another.
However that may actually not be necessary. I still have to go through the
corner cases I think.
A related questions is whether the remapping should be visible to lisp code
using face functions. For instance, does (face-attribute 'default :family)
1. return the remapped family, or 2. return the family of the `underlying'
default face?
My current patch does the former, but now I'm leaning towards making it the
latter, and having remapping be a pure display operation -- it just seems
simpler to deal with. Lisp code that's interested in such matters can look
at the variable to see what's up.
-Miles
--
`Cars give people wonderful freedom and increase their opportunities.
But they also destroy the environment, to an extent so drastic that
they kill all social life' (from _A Pattern Language_)
next prev parent reply other threads:[~2004-05-03 23:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 13:03 Buffer-local faces Miles Bader
2004-05-03 13:33 ` Miles Bader
2004-05-03 22:20 ` Richard Stallman
2004-05-03 23:19 ` Miles Bader [this message]
2004-05-04 5:56 ` Eli Zaretskii
2004-05-04 13:27 ` Stefan Monnier
2004-05-04 20:07 ` Richard Stallman
2004-05-03 22:42 ` Stefan Monnier
2004-05-03 23:27 ` Miles Bader
2004-05-04 5:45 ` Juri Linkov
2004-05-04 8:22 ` Miles Bader
2004-05-04 13:37 ` Stefan Monnier
2004-05-04 14:02 ` Miles Bader
2004-05-04 14:10 ` Stefan Monnier
2004-05-05 20:20 ` Richard Stallman
2004-05-05 20:20 ` Richard Stallman
2004-05-06 13:55 ` Miles Bader
2004-05-05 20:20 ` Richard Stallman
2004-05-05 20:43 ` Stefan Monnier
2004-05-05 8:09 ` Richard Stallman
2004-05-04 20:08 ` Richard Stallman
2004-05-04 9:18 ` David Kastrup
2004-05-04 9:57 ` Miles Bader
2004-05-04 8:40 ` Kim F. Storm
2004-05-04 9:59 ` Juri Linkov
2004-05-05 20:20 ` Richard Stallman
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=20040503231927.GA9451@fencepost \
--to=miles@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.