All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Grant Grundler <grundler@parisc-linux.org>,
	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 14:00:57 -0500	[thread overview]
Message-ID: <1060974059.3260.261.camel@fuzzy> (raw)
In-Reply-To: <1060971586.2322.213.camel@fuzzy>

On Fri, 2003-08-15 at 13:19, James Bottomley wrote:
> 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].

OK, the way you do this is to start x and then type xdpyinfo.  As part
of a general list, it should give you all the visuals (including the one
it's picked as the default).

Then, you simply choose the TrueColor visual, count its index down from
the top (starting at zero---note, this isn't the visual id xdpyinfo
gives you) and then feed this back into startx:

startx -- -cc <visual index>

So on the B180, my visuals output looks like:

  number of visuals:    8
  default visual id:  0x29
  visual:
    visual id:    0x27
    class:    PseudoColor
    depth:    8 planes
    available colormap entries:    256
    red, green, blue masks:    0x0, 0x0, 0x0
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x28
    class:    GrayScale
    depth:    8 planes
    available colormap entries:    256
    red, green, blue masks:    0x0, 0x0, 0x0
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x29
    class:    StaticColor
    depth:    8 planes
    available colormap entries:    256
    red, green, blue masks:    0x7, 0x38, 0xc0
    significant bits in color specification:    8 bits
 [...]

So to get the StaticColor visual, I issue

startx -- -cc 2

The colours are slightly off, though (my white has now got a bluish
tinge, but I assume you can find a better visual than the one I chose).

James

  reply	other threads:[~2003-08-15 19:01 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
2003-08-15 19:00     ` James Bottomley [this message]
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=1060974059.3260.261.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.