rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Steve Rezsutek <steve@endgame.gsfc.nasa.gov>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: more wishes for chrismas
Date: Fri, 4 Dec 1992 09:48:30 -0500	[thread overview]
Message-ID: <199212041448.AA16613@endgame.gsfc.nasa.gov> (raw)
In-Reply-To: Alan Watson's message of "Fri, 04 Dec 92 09:02:51 EST." <9212041402.AA03650@oldp.astro.wisc.edu>

Alan Watson <alan@oldp.astro.wisc.edu> sez...

> I very rarely make quoting errors in rc, but I used to make them all
> of the time in sh.  Quoting is one less think I have to think about,
> and that allows me to devote more attention to getting other stuff
> done.

Sounds like my experience, too.

And further...

> There are a few characters which only make sense at certain places --
> like "=" which has to be quoted in dd commands -- but at least the
> current rules have a simplicity about them.  No "foo does bar except
> for on the third Wednesday in the month if the month starts on a
> weekend."


I couldn't agree more.  One of the things I like most about rc is 
the simple rule: 'it''s either quoted, or it isn''t'.  

For things like arguments to dd, the biological CPU overhead of 
typing two extra characters is a small price to pay in exchange for 
not having to constantly think about which type of quoting to apply 
where.

If y'all want my $0.02,  I'd say 'nay' to backslash quoting...


Steve


  reply	other threads:[~1992-12-04 14:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1992-12-04 14:02 Alan Watson
1992-12-04 14:48 ` Steve Rezsutek [this message]
1992-12-05 16:21 ` Dave Mason
  -- strict thread matches above, loose matches on Subject: below --
1992-12-06  8:21 Byron Rakitzis
1992-12-05 20:52 Emin Gun Sirer
1992-12-04 22:05 Chris Siebenmann
1992-12-04 16:53 Tom Culliton x2278
1992-12-04 14:58 peter
1992-12-04 12:53 malte
1992-12-04 14:03 ` Gerry.Tomlinson
1992-12-08 15:21 ` Mark-Jason Dominus

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=199212041448.AA16613@endgame.gsfc.nasa.gov \
    --to=steve@endgame.gsfc.nasa.gov \
    --cc=rc@hawkwind.utcs.toronto.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).