From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: provide an easy way to customize inherited faces
Date: Sun, 16 Jul 2006 10:33:41 -0700 [thread overview]
Message-ID: <EIENLHALHGIMHGDOLMIMKELFCJAA.drew.adams@oracle.com> (raw)
In-Reply-To: <E1G204K-00027a-1l@fencepost.gnu.org>
In Customize, when a face inherits from another, only the
directly inherited face name appears, and it appears only as
text in an editable field. If you know what you're doing, then
you can put point in the field and use M-x
customize-face. Even then, however, the default value is
just the face name in the editable field;
What else would it be?
I meant that you see only the directly inherited face name there. You cannot
see faces inherited from that face.
Also, as Stefan pointed out, what happens if a face inherits from more than
one face - which is used as the editable text? I haven't experimented with
this - are there a series of editable fields, one for each inherited face?
there is no easy way to customize other faces in the
inheritance hierarchy.
This doesn't seem wrong, really. If you customize the other face,
that will show you whatever face it inherits from, etc.
Yes, but that is more roundabout than necessary. Most inheritance
hierarchies will be pretty shallow. Why not show all the faces that are
inherited?
When a face inherits from others, the list of inherited
faces should be shown explicitly in the Customize buffer in
some fashion. A simple list next to the editable field
(perhaps with items separated by "<"), would suffice.
If someone wants to do it, it can't hurt.
(We don't want to install it now, of course.)
Agreed - no need to do it now.
next prev parent reply other threads:[~2006-07-16 17:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-15 14:44 provide an easy way to customize inherited faces Drew Adams
2006-07-16 6:25 ` Richard Stallman
2006-07-16 17:33 ` Drew Adams [this message]
2006-07-16 12:34 ` Stefan Monnier
2006-07-16 17:02 ` Drew Adams
2006-07-17 1:41 ` 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
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=EIENLHALHGIMHGDOLMIMKELFCJAA.drew.adams@oracle.com \
--to=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 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).