9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: I RATTAN <rattan@cps.cmich.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] OT: drawterm+SPARC Solaris
Date: Wed,  1 Jun 2005 13:53:10 -0400	[thread overview]
Message-ID: <Pine.GSO.4.58.0506011349130.5296@cps207.cps.cmich.edu> (raw)
In-Reply-To: <200506011521.j51FLl214157@zamenhof.cs.utwente.nl>



On Wed, 1 Jun 2005, Axel Belinfante wrote:

> commenting out the code that initializes xscreendepth
> using DefaultDepth (maybe only necessary in my env),
> and instead setting xscreendepth explicitly in the
> blocks associated with the tests that use XMatchVisualInfo,
> and changing the order of these tests such that I use an
> xscreendepth < 24 which avoids the code that
> leads to this message.
I commented out the xscreendepth 24 else clause.

The byte order problem goes away but auth now insists
in using netkey auth approach..

-ishwar


>
> Axel.
>


      reply	other threads:[~2005-06-01 17:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01 14:35 I RATTAN
2005-06-01 15:21 ` Axel Belinfante
2005-06-01 17:53   ` I RATTAN [this message]

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=Pine.GSO.4.58.0506011349130.5296@cps207.cps.cmich.edu \
    --to=rattan@cps.cmich.edu \
    --cc=9fans@cse.psu.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).