From: bobf@plan9.bell-labs.com
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: sam for WinNT?
Date: Fri, 10 Jan 1997 16:41:40 -0500 [thread overview]
Message-ID: <97Jan10.165611est.23978@hawkwind.utcs.utoronto.ca> (raw)
one of the guys in our group, sean quinlan, has a version of sam
that works on NT. he started from the plan 9 version of sam, which
is based on libg and not libXg, and hacked the bitblt and font handling
in at a fairly low level.
he plans to make it available in binary form, which should be ok
for NT, when he gets the time to package it up. i have no idea when
that will be, but sean or i will post an announcement to this list when
it is available.
next reply other threads:[~1997-01-10 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-10 21:41 bobf [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-01-13 8:03 Nigel Roles
1997-01-10 11:50 Simon Turner
[not found] <199701031949.AA87304@ux2.cso.uiuc.edu>
1997-01-03 21:05 ` Ed Kubaitis
1997-01-03 19:40 Arnold D. Robbins
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=97Jan10.165611est.23978@hawkwind.utcs.utoronto.ca \
--to=bobf@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).