From: Ken Keefe <kaje@digitalfamily.org>
Subject: Re: Undefined color error
Date: Fri, 05 Nov 2004 10:58:02 -0600 [thread overview]
Message-ID: <1099673882.7669.3.camel@localhost> (raw)
In-Reply-To: <87oeictvio.fsf@naiad.informatimago.com>
That was it!! Thank you so much! It turns out my RgbPath was this:
RgbPath "/usr/X11R6/lib/X11/rgb.txt"
I dropped the txt, restarted X, and everything is lovely again. Thanks
again!
Ken
On Fri, 2004-11-05 at 11:55 +0100, Pascal Bourguignon wrote:
> Ken Keefe <kaje@digitalfamily.org> writes:
> > > /usr/X11R6/lib/X11/rgb.txt
> > > /usr/share/emacs/21.3/etc/rgb.txt
> >
> > I checked these files and both have RGB definitions for black. Any other
> > ideas? I recently ran a java program at the command line and received
> > the same error, so it seems to not be merely an emacs problem...
>
> Then, check whether it's well configured in /etc/X11/XF86Config
> (assuming you're using a XFree X server). There should be a section
> such as:
>
> Section "Files"
> RgbPath "/usr/X11R6/lib/X11/rgb"
> ...
> EndSection
>
> (the extension should not be provided, because it can be .txt or .db).
> Which makes me think that perhaps the file format of rgb.txt is more
> precise. My file has spaces between (or after) numbers, and two
> tabulations before the name:
>
> ...
> 255 250 250^I^Isnow
> 248 248 255^I^Ighost white
> ...
> 252 252 252 ^I^Igrey99
> 255 255 255 ^I^Igray100
> 255 255 255 ^I^Igrey100
> ...
>
> You may check quickly with: cat -t /usr/X11R6/lib/X11/rgb.txt
>
next prev parent reply other threads:[~2004-11-05 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.842.1099622665.8225.help-gnu-emacs@gnu.org>
2004-11-05 5:31 ` Undefined color error Pascal Bourguignon
2004-11-05 6:38 ` Ken Keefe
[not found] ` <mailman.872.1099637438.8225.help-gnu-emacs@gnu.org>
2004-11-05 10:55 ` Pascal Bourguignon
2004-11-05 16:58 ` Ken Keefe [this message]
[not found] ` <mailman.950.1099674445.8225.help-gnu-emacs@gnu.org>
2004-11-09 17:15 ` Michael Slass
2004-12-28 18:28 ` Tom Morris
2004-11-05 2:35 Ken Keefe
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=1099673882.7669.3.camel@localhost \
--to=kaje@digitalfamily.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).