From: Hrvoje Niksic <hniksic@iskon.hr>
Subject: Re: controlling gnus faces through .Xdefaults
Date: 31 Mar 2000 18:30:14 +0200 [thread overview]
Message-ID: <dpg0t7w19l.fsf@mraz.iskon.hr> (raw)
In-Reply-To: dsg@mitre.org's message of "31 Mar 2000 09:14:57 -0500"
dsg@mitre.org (David S. Goldberg) writes:
> I can't prove it since I don't know enough about how customize has
> been integrated into the overall (X)Emacs scheme but it appears that
> when a face is created by customize, X resources are ignored in
> favor of customize defaults.
That's not supposed to happen, at least under the original design.
The X resources code is very tricky, and it's possible that something
broke along the way. I know that at least one way of specifying the
faces broke. I specify faces like this:
XEmacs.FACENAME.attributeBackground: black
XEmacs.FACENAME.attributeForeground: white
What form do you use?
next prev parent reply other threads:[~2000-03-31 16:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-31 3:29 Jason R Mastaler
2000-03-31 14:09 ` Per Abrahamsen
2000-03-31 14:14 ` David S. Goldberg
2000-03-31 16:30 ` Hrvoje Niksic [this message]
2000-03-31 20:19 ` David S. Goldberg
2000-04-03 10:56 ` Kim-Minh Kaplan
2000-04-03 12:56 ` Hrvoje Niksic
2000-04-03 14:46 ` Kim-Minh Kaplan
2000-04-03 18:34 ` David S. Goldberg
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=dpg0t7w19l.fsf@mraz.iskon.hr \
--to=hniksic@iskon.hr \
/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).