From: James Bottomley <James.Bottomley@steeleye.com>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: Re: xchat colors (Was Re: [parisc-linux] xfree86 4.2.1-9 build problem)
Date: 15 Aug 2003 13:19:45 -0500 [thread overview]
Message-ID: <1060971586.2322.213.camel@fuzzy> (raw)
In-Reply-To: <20030815172142.GA19042@dsl2.external.hp.com>
On Fri, 2003-08-15 at 12:21, Grant Grundler wrote:
> On Thu, Aug 14, 2003 at 10:26:38PM +0000, caslivkoff@speakeasy.net wrote:
> > Just to be sure this is indeed a colormap issue,
>
> Ok - it's a color map issue.
> I added some printf's to xchat-2.0.3/fe-gtk/palette.c:palette_alloc().
>
> I'll see how hard it is to teach xchat to use it's own color map.
Perhaps take Alan's suggestion instead...give the framebuffer a Direct
or True Colour visual instead of Pseudocolour.
That will look rather strange because you'll only get two or three bits
for each primary, but it will mean that you can't run out of colours.
I'll see if I can figure out how to set this up...the documentation
appears to be a bit sparse [unless Alan has any hints].
James
next prev parent reply other threads:[~2003-08-15 18:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 22:26 xchat colors (Was Re: [parisc-linux] xfree86 4.2.1-9 build problem) caslivkoff
2003-08-15 5:41 ` Grant Grundler
2003-08-15 6:16 ` [parisc-linux] Re: xchat colors Grant Grundler
2003-08-15 6:37 ` Jan-Benedict Glaw
2003-08-30 5:06 ` Grant Grundler
2003-08-15 17:21 ` xchat colors (Was Re: [parisc-linux] xfree86 4.2.1-9 build problem) Grant Grundler
2003-08-15 18:19 ` James Bottomley [this message]
2003-08-15 19:00 ` James Bottomley
2003-08-16 0:43 ` Alan Cox
2003-08-17 10:03 ` Jan-Benedict Glaw
2003-08-16 15:18 ` Chuck Slivkoff
2003-08-19 5:08 ` Grant Grundler
2003-08-21 5:11 ` [parisc-linux] Re: xchat colors Grant Grundler
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=1060971586.2322.213.camel@fuzzy \
--to=james.bottomley@steeleye.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=grundler@parisc-linux.org \
--cc=parisc-linux@lists.parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.