From: Roman Shaposhnik <roman@shaposhnik.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Practical issue on using rc shell
Date: Fri, 13 Nov 2009 12:55:57 -0800 [thread overview]
Message-ID: <e763acc10911131255g14679929ka878005309b3e5f4@mail.gmail.com> (raw)
In-Reply-To: <b98d3e520911131246yb7e32f6id939cce77ac394d0@mail.gmail.com>
On Fri, Nov 13, 2009 at 12:46 PM, pmarin <pacogeek@gmail.com> wrote:
> fortunately, the unix world is less radical, you can use rlfe
> http://per.bothner.com/software/
There's also versatile socat:
http://www.dest-unreach.org/socat/doc/socat.html#EXAMPLE_ADDRESS_READLINE
Thanks,
Roman.
next prev parent reply other threads:[~2009-11-13 20:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 18:41 Maurício CA
2009-11-13 18:52 ` erik quanstrom
2009-11-13 18:54 ` Tim Newsham
2009-11-13 19:02 ` David Leimbach
2009-11-13 20:46 ` pmarin
2009-11-13 20:50 ` Venkatesh Srinivas
2009-11-13 20:55 ` Roman Shaposhnik [this message]
2009-11-13 21:00 ` Nick LaForge
2009-11-13 21:10 ` pmarin
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=e763acc10911131255g14679929ka878005309b3e5f4@mail.gmail.com \
--to=roman@shaposhnik.org \
--cc=9fans@9fans.net \
/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).