rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Scott Schwartz <schwartz@groucho.cse.psu.edu>
To: Alan Watson <alan@oldp.astro.wisc.edu>
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: rc FAQ list
Date: Sat, 24 Jul 1993 21:16:45 -0400	[thread overview]
Message-ID: <93Jul24.211605edt.2591@groucho.cse.psu.edu> (raw)
In-Reply-To: Your message of "Sat, 24 Jul 1993 20:44:42 EDT." <9307250044.AA21203@oldp.astro.wisc.edu>

| Is it just me, or do these people really have their
| own version of reality?

Doesn't everybody?  :-)

A friend of mine used to say, "who needs tcsh when you can run
rc in an emacs shell buffer".  

Anyway, zsh does have some good ideas that it wouldn't hurt rc to adopt
(ok, ok, es maybe.:-)).   My two favorites: builtin read, and recursive

  reply	other threads:[~1993-07-25  1:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-07-25  0:44 Alan Watson
1993-07-25  1:16 ` Scott Schwartz [this message]
1993-07-26  9:33   ` Richard Brooksby
1993-07-26  9:58     ` Tim.Goodwin
1993-07-25  2:36 ` Dennis Colarelli
1993-07-25  3:06 Alan Watson
1993-09-04 18:46 Alan Watson

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=93Jul24.211605edt.2591@groucho.cse.psu.edu \
    --to=schwartz@groucho.cse.psu.edu \
    --cc=alan@oldp.astro.wisc.edu \
    --cc=rc@hawkwind.utcs.toronto.edu \


* 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).