From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: plan9port: recent changes
Date: Mon, 14 Feb 2005 22:39:17 -0500 [thread overview]
Message-ID: <ee9e417a05021419393040f5cd@mail.gmail.com> (raw)
In-Reply-To: <6.0.2.0.0.20050215162332.01b5bf18@pop.monitorbm.co.nz>
> I occasionally have a look at it. The likes of libfmt/libutf/libregexp
> build pretty much straight out of the box, but I can't get over the hurdle
> of libdraw, which I'm too lazy/ignorant/stupid/busy to make much headway
> on. Would the drawterm implementation provide any pointers as to how to
> proceed? The X version in drawterm seems at first sight quite different
> from the plan9port version.
They're very similar. You may need to look past initdraw.
Russ
next prev parent reply other threads:[~2005-02-15 3:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-14 0:41 [9fans] " Russ Cox
2005-02-14 19:09 ` [9fans] " Russ Cox
2005-02-14 20:31 ` Bruce Ellis
2005-02-14 20:49 ` Russ Cox
2005-02-14 21:03 ` Skip Tavakkolian
2005-02-15 3:28 ` Andrew Simmons
2005-02-15 3:39 ` Russ Cox [this message]
2005-02-15 7:20 ` Tiit Lankots
2005-02-15 9:51 ` David Tolpin
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=ee9e417a05021419393040f5cd@mail.gmail.com \
--to=russcox@gmail.com \
--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).