9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Paul Lalonde <plalonde@telus.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: request: native graphics on OS X
Date: Sun, 10 Dec 2006 16:05:58 -0800	[thread overview]
Message-ID: <70F10AFD-ADF5-4380-9B2F-CEBD44FCB40B@telus.net> (raw)
In-Reply-To: <ee9e417a0612101541i13afcb7aubb5fbd3e5c42b50d@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

It's not a deep guilt.  I can stand to throw a little back to the  
community.

And wow, that is miles simpler.  I'll see if I can't get it going.

Paul

On 10-Dec-06, at 3:41 PM, Russ Cox wrote:

>> Ok, my guilt is getting me to spend a couple of hours on this this
>> afternoon.
>> I'm assuming I just need to reimplement src/cmd/devdraw?
>
> I didn't mean to guilt anyone into action.
> Working on either src/cmd/devdraw or a new
> drawterm/gui-mac directory would be fine.
>
> You should look at the drawterm/gui-win32
> directory either way, since it shows how
> much simpler the hook code can be if you're
> not trying to make remote network graphics
> work well.
>
> Russ

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFFfKDmpJeHo/Fbu1wRAh7XAJ9Zh9P+RPWj0+7Xts3+z4gRPtNnVwCcCcy7
55XgwasogzwEZayJikzETU4=
=h88i
-----END PGP SIGNATURE-----


  reply	other threads:[~2006-12-11  0:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-10 22:33 [9fans] " Russ Cox
2006-12-10 23:01 ` [9fans] " Russ Cox
2006-12-10 23:23   ` Paul Lalonde
2006-12-10 23:41     ` Russ Cox
2006-12-11  0:05       ` Paul Lalonde [this message]
2006-12-11  1:38   ` Paul Lalonde
2007-01-09 21:39     ` David Leimbach
2007-01-09 22:22       ` Russ Cox
2007-01-09 22:42         ` Paul Lalonde
2007-01-10  0:05         ` Brantley Coile
2007-01-10  0:58           ` andrey mirtchovski
2007-01-10  1:01             ` Brantley Coile
2007-01-10  1:05             ` andrey mirtchovski
2007-01-10  1:07               ` Brantley Coile
2007-01-10  1:24                 ` andrey mirtchovski
2007-01-10  5:09                   ` David Leimbach
2007-01-10  5:18                     ` andrey mirtchovski
2007-01-10  1:05             ` Paul Lalonde
2007-01-10 16:39           ` Abhey Shah
2007-01-10 16:46             ` David Leimbach
2007-01-10  9:20         ` Skip Tavakkolian
2007-01-10 16:07           ` David Leimbach
2007-01-10 16:39             ` Paul Lalonde
     [not found] <3e1162e60701100853g5fdfcd3biee499db044d08c2d@mail.gmail.com>
     [not found] ` <000623fb1023a5f733c3334516192f41@9netics.com>
     [not found]   ` <3e1162e60701101131h71bbfc70oee234fc314fc0ade@mail.gmail.com>
     [not found]     ` <3e1162e60701101140y441d2d88w85dbce3611149084@mail.gmail.com>
     [not found]       ` <3e1162e60701101151m38efec2do8027141a8ac4115c@mail.gmail.com>
2007-01-10 20:03         ` Fwd: " David Leimbach
2007-01-11 22:43           ` andrey mirtchovski
2007-01-11 22:48             ` David Leimbach
2007-01-11 22:53               ` andrey mirtchovski
2007-01-11 22:54               ` David Leimbach

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=70F10AFD-ADF5-4380-9B2F-CEBD44FCB40B@telus.net \
    --to=plalonde@telus.net \
    --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).