rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: culliton@srg.af.mil (Tom Culliton x2278)
To: rc@hawkwind.utcs.toronto.edu
Subject: Raising the flag
Date: Tue, 7 Dec 1993 20:45:18 -0500	[thread overview]
Message-ID: <9312072045.aa11960@ceres.srg.af.mil> (raw)

Things here on the mailing list have been quiet for far too long.  It
seems like time to stir them up a bit before the holidays.  So since
I've never been one to leave well enough alone, I'll take Byron Claus at
his word about 1.5: ;-) ;-) ;-)

> From: Byron Rakitzis <byron@netapp.com>
> Date:   Sun, 19 Sep 1993 16:48:19 -0400
> ... once the smoke clears I will possibly have some time to
> concentrate on rc. Bug me in a few weeks again..

So how are things going?  Still busier than a one legged man in a butt
kicking contest?  Any chance for 1.5 in the new year?  Anything we can
do to help?

Of course 1.4 continues to perform flawlessly and unobtrusively, day in
and day out, quietly making short work of the ugliest shell problems. 
For other "Doctor Who" fans, it reminds me of the laser probe that could
"remove the atoms from a molecule one by one, or punch a fist size hole
through six inch armor plate".  (I'm sure someone will be able to
correct me and even name the episode the quote is from.)


ObRC - When you wrap a builtin like cd with a function, be sure that you
remember to propagate the result.  I gave myself a nasty fright when:

    if (cd $invalid_directory) { ... }

thought that the cd had succeeded, because my cd function didn't save
$status before updating $prompt and return the saved value.  Luckily,
testing the script caught this.  Caveat Utor!

             reply	other threads:[~1993-12-08  2:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-12-08  1:45 Tom Culliton x2278 [this message]
1993-12-08  6:12 Byron Rakitzis

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=9312072045.aa11960@ceres.srg.af.mil \
    --to=culliton@srg.af.mil \
    --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).