From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: .Xresources
Date: Wed, 13 Feb 2008 18:36:42 +1100 [thread overview]
Message-ID: <87tzkdtiid.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: mailman.7355.1202858373.18990.help-gnu-emacs@gnu.org
Peter Dyballa <Peter_Dyballa@Web.DE> writes:
> Am 12.02.2008 um 21:46 schrieb Sean Sieger:
>
>> If I have
>>
>> Emacs.pointerColor: red
>>
>> in my .Xresources, then why would it still be white?
>
> Because mine is red now! Although I have:
>
> Emacs*pointerColor: DarkOrchid4
>
> Actually it's red in all my GNU Emacsen 23.0.x ... Looks like a bug.
>
> --
> Greetings
>
> Pete
>
> Claiming that the Macintosh is inferior to Windows because most people use
> Windows, is like saying that all other restaurants serve food that is
> inferior to McDonald's.
>
I have mine set to white and its white. This is in emacs 22.1 and CVS
emacs
The problem may be related to how your .Xresources is loaded (i.e. xrdb
load versus xrdb merge) and how you define the resource
e.g. Emacs.pointerColor versus emacs.pointerColor versus
Emacs*ponterColor etc.
I'd try an xrdb load and see if that helps (working from memory, but I
think when you do a merge, your local .Xresources won't override a more
'specific' setting that may be in a site wide app-defaults file. Check
the manual for xrdb - its been a long time since I last read it and I
could easily be wrong.
Other possible causes -
- Some window managers can override things - notably KDE
- .emacs settings will override .Xresources I think because they are
loaded last. Maybe there is a setting in there
- Using the color themes package with a theme that sets the pointer
- color.
Tim
--
tcross (at) rapttech dot com dot au
next prev parent reply other threads:[~2008-02-13 7:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 20:46 .Xresources Sean Sieger
2008-02-12 23:19 ` .Xresources Peter Dyballa
[not found] ` <mailman.7355.1202858373.18990.help-gnu-emacs@gnu.org>
2008-02-13 7:36 ` Tim X [this message]
2008-02-13 10:39 ` .Xresources Peter Dyballa
2008-02-13 15:10 ` .Xresources Peter Dyballa
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=87tzkdtiid.fsf@lion.rapttech.com.au \
--to=timx@nospam.dev.null \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).