From: Leonard Blanks <ltb@haruspex.demon.co.uk>
Subject: Re: gnus-pointer.xp[b]m background colour
Date: 23 Sep 1997 15:51:37 +0000 [thread overview]
Message-ID: <m2pvq03u5y.fsf@haruspex.demon.co.uk> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "23 Sep 1997 06:46:02 +0200"
>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
Lars> Leonard Blanks <ltb@haruspex.demon.co.uk> writes:
>> ,-----
>> | /* colors */
>> | ". c #0000ff",
>> | "# c #ebebeb s backgroundToolBarColor",
>> `-----
>>
>> Am I reading this correctly and, if so, shouldn't the modeline
>> background colour be specified instead?
Lars> Yes... and what is the modeline background color name?
I am beginning to understand the reason for the universal use of the
toolbar background colours in the Gnus xpm files, since - it seems -
the toolbar is a "real" Xt widget and the modeline is not (or at least
not in the same sense as the toolbar is, having its own colour and
shading names). This is implied in the XEmacs source, at least to
this noddy, and indicated as well in the .Xdefault settings:
Emacs.modeline*attributeBackground
vs.
Emacs*backgroundToolBarColor
It would be easy enough for me to customize the xpm file, but a more
general solution would have been nice.
Just out of curiosity, would a setting of "none" provide an
acceptable general solution if my assumptions about modeline as a
second-class widget with no "proper" background colour name are true?
--
Len
next prev parent reply other threads:[~1997-09-23 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-23 0:03 Leonard Blanks
1997-09-23 4:46 ` Lars Magne Ingebrigtsen
1997-09-23 14:21 ` Hrvoje Niksic
1997-09-24 1:28 ` SL Baur
1997-09-23 15:51 ` Leonard Blanks [this message]
1997-09-23 23:53 ` Lars Magne Ingebrigtsen
1997-09-24 1:31 ` SL Baur
1997-09-24 22:12 ` Lars Magne Ingebrigtsen
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=m2pvq03u5y.fsf@haruspex.demon.co.uk \
--to=ltb@haruspex.demon.co.uk \
/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).