From: "James A. Robinson" <jim.robinson@stanford.edu>
To: Jim Crigler <criglerj@yahoo.com>
Cc: sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: sam-9libs vs. Linux (RH 6.0)
Date: Tue, 28 Mar 2000 13:28:56 -0500 [thread overview]
Message-ID: <200003281828.KAA18140@highwire.stanford.edu> (raw)
In-Reply-To: Message from Jim Crigler <criglerj@yahoo.com> of "Tue, 28 Mar 2000 10:15:41 PST."References: <20000328181541.26330.qmail@web3203.mail.yahoo.com> <20000328181541.26330.qmail@web3203.mail.yahoo.com>
> 16-bit X works, thanks. Neither 24 nor 32 works,
> however. Is this likely to be a libXg problem or
> something in samterm per se?
I seem to recall it was a libXg problem. Someone explained that part of
the code expects the depth to be have some properties that don't apply
to 24bit depth (or, I guess, 32bit). I'm sorry that I don't remember
the details.
Jim
next prev parent reply other threads:[~2000-03-28 23:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-28 18:15 Jim Crigler
2000-03-28 18:28 ` James A. Robinson [this message]
2000-03-29 0:07 ` Daniel Neri
2000-03-29 5:10 ` Scott Schwartz
-- strict thread matches above, loose matches on Subject: below --
2000-03-29 4:12 Jim Crigler
2000-03-27 13:52 Jim Crigler
2000-03-27 20:54 ` James A. Robinson
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=200003281828.KAA18140@highwire.stanford.edu \
--to=jim.robinson@stanford.edu \
--cc=criglerj@yahoo.com \
--cc=sam-fans@hawkwind.utcs.toronto.edu \
/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 NNTP newsgroup(s).