From: dsg@linus.mitre.org (David S. Goldberg)
Subject: replacement for custom-face-lookup
Date: 06 Oct 1997 14:12:48 -0400 [thread overview]
Message-ID: <m1biuvalpzz.fsf@blackbird.mitre.org> (raw)
OK, so the XEmacs guys got their way and custom-face-lookup is gone.
I'm not going to waste time arguing the decision since I don't know
why it was considered evil. I just know that as a result I can't get
qgnus 0.12 working because I used custom-face-lookup in my .gnus for
setting the gnus-cite-list, gnus-header-face-alist and
gnus-summary-highlight. What should I use to replace it? Do I really
have to do all that make-face stuff by hand or is there some other
reasonable alternative? I've looked at the custom documentation. It
appears that defface may be what I want, but I'm really not interested
in setting up all the menu stuff that comes with it. So if there's
any other alternative I'd like to know it.
Thanks,
--
Dave Goldberg
Post: The Mitre Corporation\MS B305\202 Burlington Rd.\Bedford, MA 01730
Phone: 781-271-3887
Email: dsg@mitre.org
next reply other threads:[~1997-10-06 18:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-06 18:12 David S. Goldberg [this message]
1997-10-06 18:45 ` Per Abrahamsen
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=m1biuvalpzz.fsf@blackbird.mitre.org \
--to=dsg@linus.mitre.org \
--cc=dsg@mitre.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.
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 NNTP newsgroup(s).