From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: Samx - one more time ...
Date: Thu, 27 Apr 2000 16:17:43 -0400 [thread overview]
Message-ID: <00Apr27.232209edt.24768@hawkwind.utcs.toronto.edu> (raw)
One thing: Does this mean that libXg also needs changes?
The graphics model has changed quite a bit,
and there is not currently anything approximating
libXg, at least in such a form. I have vague notions
of it being a nice thing to have a libXg equivalent
for the new graphics model, and I do have many
of the pieces, but not all, and they're not packaged
correctly.
Rob should correct me if I'm wrong, but I believe
that the protocol between sam and samterm has not
changed, so that you could pick up the aforementioned
sam changes and keep using the current samterm,
if you were not inclined to do battle with X.
Russ
next reply other threads:[~2000-04-28 3:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-27 20:17 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-04-27 8:04 Bengt Kleberg
2000-04-26 22:34 Paul Jackson
2000-04-26 22:26 Paul Jackson
2000-04-26 20:25 Paul Jackson
2000-04-25 14:38 Bengt Kleberg
2000-04-25 12:42 rob pike
2000-04-21 2:08 Paul Jackson
2000-04-25 10:59 ` Alex Danilo
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=00Apr27.232209edt.24768@hawkwind.utcs.toronto.edu \
--to=rsc@plan9.bell-labs.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).