From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] How to move to rc from sh/bash
Date: Sat, 9 Feb 2008 04:00:21 -0500 [thread overview]
Message-ID: <7420c84252850512236ab0ad6ce98879@quanstro.net> (raw)
In-Reply-To: <b954b2060802082353h694ee9a3kd008351835d9f27a@mail.gmail.com>
> 1. Is it possible to do command line edit in rc?
> That is, in bash, both emacs and vi like keybindings can be used
> (thanks to readline library). But in rc, I have not noticed that yet.
> As a result, some basic usuages of a shell, such as recalling the
> previously executed commands, have to be done by mouse (snarf and
> paste).
command line editing is provided by acme in the case of win, or
rio(1) directly. not hold mode entered by typing <esc>.
> 2. In non-interactive use (script programming), what's the main
> advantages of rc over sh/bash?
tom duff's original paper is in /sys/doc/rc.ps. i don't think i can
make a better argument for rc than that. personally, i think the
regularized grammer and quoting pay big dividends. rc is also
small. it's not hard to understand the virtual machine its built
around. but you'll need to decide for your self.
- erik
next prev parent reply other threads:[~2008-02-09 9:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 7:53 Hongzheng Wang
2008-02-09 8:01 ` mattmobile
2008-02-09 8:41 ` Hongzheng Wang
2008-02-09 8:57 ` mattmobile
2008-02-09 9:00 ` erik quanstrom [this message]
2008-02-09 9:21 ` Hongzheng Wang
2008-02-09 10:11 ` Charles Forsyth
2008-02-09 10:27 ` Lluís Batlle
2008-02-09 15:06 ` Uriel
2008-02-09 17:54 ` Charles Forsyth
2008-02-09 21:59 ` geoff
2008-02-09 13:00 ` Anthony Sorace
2008-02-10 16:59 ` Gorka Guardiola
2008-02-10 17:16 ` Pietro Gagliardi
2008-02-10 17:47 ` erik quanstrom
2008-02-10 18:12 ` Martin Neubauer
2008-02-11 15:04 ` erik quanstrom
2008-02-11 23:03 ` Martin Neubauer
2008-02-11 23:25 ` Pietro Gagliardi
2008-02-20 15:04 ` maht
2008-02-20 15:08 ` Federico G. Benavento
2008-02-20 15:24 ` erik quanstrom
2008-02-20 15:55 ` maht
2008-02-11 23:59 ` Uriel
2008-02-12 11:57 ` Martin Neubauer
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=7420c84252850512236ab0ad6ce98879@quanstro.net \
--to=quanstro@quanstro.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).