From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: rc@hawkwind.utcs.toronto.edu, tjg@star.le.ac.uk
Subject: Re: ifs substitution, how should it work?
Date: Fri, 19 May 2000 18:10:01 -0400 [thread overview]
Message-ID: <00May21.004230edt.26277@hawkwind.utcs.toronto.edu> (raw)
Introducing contexts where singleton lists
and strings are not identical seems a very bad idea.
Then you have to explain that in general they
are but ifs isn't; and what if save ifs away
to another variable and then restore it?
What does "x=(abc); ifs=$x" do?
If you want basename, why not use basename or sed or awk?
Russ
next reply other threads:[~2000-05-21 4:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-19 22:10 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-05-22 7:55 Bengt Kleberg
2000-05-22 8:53 ` Tim Goodwin
2000-05-18 12:57 Bengt Kleberg
2000-05-18 8:12 Bengt Kleberg
2000-05-18 12:12 ` Tim Goodwin
2000-05-18 6:32 Byron Rakitzis
2000-05-16 11:22 Bengt Kleberg
2000-05-12 10:14 Bengt Kleberg
2000-05-15 9:27 ` Tim Goodwin
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=00May21.004230edt.26277@hawkwind.utcs.toronto.edu \
--to=rsc@plan9.bell-labs.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).