From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] I did it (curses port)
Date: Sat, 28 Apr 2007 21:14:04 -0400 [thread overview]
Message-ID: <6e0b4ec1a5f137d26106828b7c598214@coraid.com> (raw)
In-Reply-To: <656a0f9ebd7d8661da917a98739ef837@yourdomain.dom>
could you inform the ignorant? what advantage does lynx
have over abaco?
- erik
On Sat Apr 28 10:29:40 EDT 2007, benavento@gmail.com wrote:
> yes, it's true I have ported PDCurses 3.0 to Plan 9, it doesn't need vt(1)
> and it even has mouse support.
>
> http://www.tip9ug.jp/who/fgb/lynx.png - screenshot
> /n/sources/contrib/fgb/curses.tgz - what you all wanted ;)
> /n/sources/contrib/fgb/lynx.tgz - binary and cfg files
next prev parent reply other threads:[~2007-04-29 1:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 14:29 Federico G. Benavento
2007-04-29 1:14 ` erik quanstrom [this message]
2007-04-29 2:03 ` Federico Benavento
2007-04-29 12:51 ` erik quanstrom
2007-04-29 14:47 ` George Gensure
2007-05-02 20:28 ` Harri Haataja
2007-05-02 21:22 ` C H Forsyth
2007-05-02 21:31 ` Devon H. O'Dell
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=6e0b4ec1a5f137d26106828b7c598214@coraid.com \
--to=quanstro@coraid.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).