From: malte@TechFak.Uni-Bielefeld.DE
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: here strings
Date: Sat, 5 Jun 1993 08:53:13 -0400 [thread overview]
Message-ID: <9306051253.AA09468@idefix.techfak.uni-bielefeld.de> (raw)
a directory full of files that had come from, ah, another operating
system, and the names were all upper-case:
for (f in *) mv $f `{tr A-Z a-z <<<$f}
OK,
John.
Your lucky this worked because most (especially on older unixes) text
utilities require their input to end in a '\n'. Then you'd have to
for (f in *) mv $f `{echo $f | tr A-Z a-z}
Malte
next reply other threads:[~1993-06-05 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-06-05 12:53 malte [this message]
1993-06-05 12:55 ` John Mackin
[not found] <john@civil.su.oz.au>
1993-06-07 8:42 ` malte
-- strict thread matches above, loose matches on Subject: below --
1993-06-05 16:42 Alan Watson
1993-06-05 12:35 John Mackin
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=9306051253.AA09468@idefix.techfak.uni-bielefeld.de \
--to=malte@techfak.uni-bielefeld.de \
--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).