From: reader@newsguy.com
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: X resources contorl file
Date: Wed, 15 Nov 2006 20:37:57 -0600 [thread overview]
Message-ID: <87d57ounei.fsf@newsguy.com> (raw)
In-Reply-To: 455B73A4.3070004@gmail.com
Nagatoro <nagatoro@gmail.com> writes:
> reader@newsguy.com wrote:
> [...]
>> Currently the .xresoruces file appears to be ignored.
>
> Try with a capital X (.Xresources).
Haa.. there was a time and maybe different OS where case didn't matter
so I never thought to try that.
Even this time, I quickly tried it and saw no difference and was on
the verge of posting back saying it didn't change anything but I
pondered a moment and thought to try restarting X. Sure enough, the
lowercase was the problem. On restarting X the data in .Xresources
was recognized.
I'd quit even using it mnths ago and am glad to have it back...Thanks.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-11-16 2:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 19:48 [gentoo-user] X resources contorl file reader
2006-11-15 20:08 ` Nagatoro
2006-11-16 2:37 ` reader [this message]
2006-11-16 6:36 ` [gentoo-user] " Alan McKinnon
2006-11-16 7:45 ` reader
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=87d57ounei.fsf@newsguy.com \
--to=reader@newsguy.com \
--cc=gentoo-user@lists.gentoo.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