From: "Fco. J. Ballesteros" <nemo@gsyc.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Réf. : Re: [9fans] Silly porting fun (RC for Unix)
Date: Tue, 18 Jul 2000 09:29:30 +0100 [thread overview]
Message-ID: <14708.5482.591508.898668@nautilus.dat.escet.urjc.es> (raw)
In-Reply-To: <200007171910.MAA11630@ohio.river.org>
>>>>> "Richard" == Richard <ru@ohio.river.org> writes:
Richard> boyd roberts writes:
>> used the unix rc for years; well written, solid as a rock.
Richard> do you 2 use it as your interactive shell, too, or just
Richard> for scripts?
I use it for both. Very convenient. BTW, on ux you can use the
readline klud^H^H^H library so that rc can edit the command line.
--
() ascii ribbon campaign - against html mail
/\ - against microsoft attachments
prev parent reply other threads:[~2000-07-18 8:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-17 10:21 boyd.roberts
2000-07-17 10:29 ` [9fans] " Randolph Fritz
2000-07-18 6:30 ` [9fans] " Lucio De Re
2000-07-18 7:16 ` Richard
2000-07-18 7:58 ` [9fans] " Lucio De Re
2000-07-17 19:10 ` Richard
2000-07-17 19:49 ` [9fans] " Randolph Fritz
2000-07-18 8:25 ` Steve Simon
2000-07-18 8:29 ` Fco. J. Ballesteros [this message]
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=14708.5482.591508.898668@nautilus.dat.escet.urjc.es \
--to=nemo@gsyc.escet.urjc.es \
--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).