From: Chong Yidong <cyd@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, 11059@debbugs.gnu.org
Subject: bug#11059: 24.0.94; Please add `face-spec-set' to the elisp manual
Date: Thu, 12 Apr 2012 23:13:48 +0800 [thread overview]
Message-ID: <87ehrt56fn.fsf@gnu.org> (raw)
In-Reply-To: <jwvzkah6quu.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 12 Apr 2012 09:10:18 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Indeed, but this has some downsides: Custom may decide to rewrite your
> handwritten custom-set-faces. We should document an Elisp way to
> configure faces, and I'd recommend a new function `custom-set-face'
> which works just like custom-set-faces except it applies to a single
> face and will be left alone by Custom.
We already have a multitude of Elisp ways to configure faces:
set-face-attribute, X resources, various frame parameters,
default-frame-alist, face-new-frame-defaults... Throwing yet another
function into the current mix is not a pleasing prospect.
The issue is that, as you know, at a fundamental Emacs treats faces in
terms of face attributes; face *specs* are a higher-level construct
recognized only by the Custom system and the related frame creation
code. So the equivalent of `setq-default' for faces is
`set-face-attribute', which works on attributes not specs.
I'd prefer reforming the system by changing the C code to understand and
store face specs. Then the equivalent of `setq-default' for faces would
be to change an entry in `face-new-frame-defaults'---which would store
face specs rather than what vectors of attributes (almost all
unspecified) as it currently does. Probably not difficult, but more
suitable for Emacs 25 than 24.2.
next prev parent reply other threads:[~2012-04-12 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 23:35 bug#11059: 24.0.94; Please add `face-spec-set' to the elisp manual Michael Heerdegen
2012-04-11 6:08 ` Chong Yidong
2012-04-11 17:05 ` Michael Heerdegen
2012-04-12 7:00 ` Chong Yidong
2012-04-12 13:10 ` Stefan Monnier
2012-04-12 14:17 ` Drew Adams
2012-04-12 15:13 ` Chong Yidong [this message]
2012-04-12 16:04 ` Stefan Monnier
2012-04-12 15:14 ` Chong Yidong
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=87ehrt56fn.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=11059@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
/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).