From: Harri Haataja <harriha@mail.student.oulu.fi>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] I did it (curses port)
Date: Wed, 2 May 2007 23:28:53 +0300 [thread overview]
Message-ID: <20070502202852.GA8353@paju.oulu.fi> (raw)
In-Reply-To: <b47db0340704290747ma0aa829jfa4cff633fba84a1@mail.gmail.com>
On Sun, Apr 29, 2007 at 10:47:13AM -0400, George Gensure wrote:
> >I don't like curses myself and I didn't just for fun, but I see this
> >could be useful to some people (like emacs fanboys).
> >Also we could make the perl, tcl and python ports use it.
> >this will give as a few more apps.
> >
> vi and nethack fanboys as well (like myself)
Yay. Would this also get readline and command history (rlwrap)?
Purely for rio-less installation, of course *cough*
next prev parent reply other threads:[~2007-05-02 20:28 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
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 [this message]
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=20070502202852.GA8353@paju.oulu.fi \
--to=harriha@mail.student.oulu.fi \
--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).