From: smd@clock.org
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: New rc snapshot, includes "the equals hack"
Date: Tue, 15 Aug 2000 09:32:30 -0500 [thread overview]
Message-ID: <20000815133234Z3021-8597+4@cesium.clock.org> (raw)
Maybe I'm a bit of a crank, but I think for scripting work,
the "equals hack" really doesn't buy much; the only time I
even ponder it is when I am doing interactive work and forget
that "arguments containing special characters must be quoted".
Although I know that dd, make, and some GNU utilities like
arguments which contain one of rc's special characters, and
this can be frustrating if one forgets, I don't see why we
should necessarily have:
: sean(rc) ; echo foo=a
foo=a
but
: sean(rc) ; echo foo^a
fooa
: sean(rc) ; echo foo&a
12978
a not found
foo
: sean(rc) ; echo foo;a
foo
a not found
: sean(rc) ; echo foo$a
foo
and so forth. One of the neat things about rc is that there
are few syntactic surprises; I think a rule that says "quote your arguments"
and especially "arguments with special characters MUST be quoted" is
consistent.
Sean.
next reply other threads:[~2000-08-15 20:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-15 14:32 smd [this message]
2000-08-15 22:51 ` Smarasderagd
2000-08-17 3:53 ` Decklin Foster
2000-08-21 23:21 ` Chris Siebenmann
2000-08-22 11:51 ` Carlo Strozzi
2000-08-17 10:49 ` Tim Goodwin
-- strict thread matches above, loose matches on Subject: below --
2000-08-23 1:03 Byron Rakitzis
2000-08-22 0:28 Byron Rakitzis
2000-08-22 23:23 ` Chris Siebenmann
2000-08-18 21:14 Bengt Kleberg
2000-08-15 20:25 smd
2000-08-15 7:28 Byron Rakitzis
2000-08-15 6:41 Byron Rakitzis
2000-08-11 14:01 Tim Goodwin
2000-08-15 2:21 ` Paul Haahr
2000-08-15 4:21 ` Gary Carvell
2000-08-15 14:52 ` Mark K. Gardner
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=20000815133234Z3021-8597+4@cesium.clock.org \
--to=smd@clock.org \
--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).