rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Byron Rakitzis <byron@rakitzis.com>
Cc: tjg@star.le.ac.uk, rc@hawkwind.utcs.toronto.edu
Subject: Re: building rc on QNX4
Date: Sat, 6 May 2000 12:35:04 -0400	[thread overview]
Message-ID: <XFMail.20000506093504.jeremy@goop.org> (raw)
In-Reply-To: <200005040845.BAA09376@rakitzis.com>


On 04-May-2000 Byron Rakitzis wrote:
>> to rc with a longer and more meaningful name, like 'rcsh'.
> 
> I guess I can't shut up -- "rcsh" seems like an abominable name.
> 
> rc has nothing to do with csh or any of the {tzck}sh family.
> 
> We may as well call it "rash".

9sh would be consistent with some other names (9term, 9wm, etc).  But I prefer
rc.

        J


  parent reply	other threads:[~2000-05-06 21:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-04  8:45 Byron Rakitzis
2000-05-06 10:28 ` Carlo Strozzi
2000-05-07 17:46   ` Paul Haahr
2000-05-08  8:01     ` Carlo Strozzi
2000-05-06 16:35 ` Jeremy Fitzhardinge [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-05-09  4:34 Smarasderagd
2000-05-11 12:26 ` Gert-Jan Vons
2000-05-08 15:23 Sam Roberts
2000-05-09  8:25 ` Carlo Strozzi
2000-05-08 15:15 Smarasderagd
2000-05-09  8:22 ` Carlo Strozzi
2000-05-08 10:19 Bengt Kleberg
2000-05-06 21:47 Byron Rakitzis
2000-05-04 13:46 Sam Roberts
     [not found] <sroberts@uniserve.com>
2000-04-26 15:02 ` Sam Roberts
2000-04-27 16:56   ` Scott Schwartz
2000-04-27 20:41     ` Sam Roberts
2000-04-27 17:39   ` Carlo Strozzi
2000-05-02 14:41     ` Tim Goodwin
2000-05-04 15:18       ` Carlo Strozzi
2000-05-08  8:29         ` Tim Goodwin
2000-05-08  8:58           ` Chris Siebenmann
2000-05-08  9:15             ` Tim Goodwin
2000-05-08 23:25               ` Stephen Tell
2000-05-08 11:50           ` David Luyer
2000-05-08 13:28           ` Carlo Strozzi

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=XFMail.20000506093504.jeremy@goop.org \
    --to=jeremy@goop.org \
    --cc=byron@rakitzis.com \
    --cc=rc@hawkwind.utcs.toronto.edu \
    --cc=tjg@star.le.ac.uk \
    /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).