From: Tim Goodwin <tjg@star.le.ac.uk>
To: Bengt Kleberg <bengt@softwell.se>
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: ifs substitution, how should it work?
Date: Thu, 18 May 2000 08:12:38 -0400 [thread overview]
Message-ID: <QB8AAEzeIznNPA8A@ltsun0.star.le.ac.uk> (raw)
In-Reply-To: <200005180812.KAA05394@trillian.softwell.se>
> ; x = ``(abc) {echo -n 1a2b3abc4c5}
> ; echo $x => 1a2b3 4c5
If you want awk, you know where to find it. :-)
I don't think anything more complicated than single character field
seperators belongs in a shell: particularly not rc.
What's the actual problem you're trying to solve?
Tim.
next prev parent reply other threads:[~2000-05-19 22:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-18 8:12 Bengt Kleberg
2000-05-18 12:12 ` Tim Goodwin [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-19 22:10 Russ Cox
2000-05-18 12:57 Bengt Kleberg
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=QB8AAEzeIznNPA8A@ltsun0.star.le.ac.uk \
--to=tjg@star.le.ac.uk \
--cc=bengt@softwell.se \
--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).