From: John (Most modern computers would break if you stood on them) Mackin <john@ civil.su.oz.au>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: here strings
Date: Sat, 5 Jun 1993 08:55:54 -0400 [thread overview]
Message-ID: <199306052255.25518.rc.bakay@civil.su.oz.au> (raw)
In-Reply-To: <9306051253.AA09468@idefix.techfak.uni-bielefeld.de>
[Me:]
for (f in *) mv $f `{tr A-Z a-z <<<$f}
[Malte:]
Your [sic] lucky this worked because most (especially on older unixes) text
utilities require their input to end in a '\n'.
(let ((high-horse 'on))
Normally, I'd keep this private, but since Malte chose to toss a dart at my
reputation on the list, I am replying to the same place.
I have been a Unix professional for over ten years, and I am certainly
N O T `lucky this worked.' I knew damn well that it would work. I am
keenly aware of this historical development of Unix commands, and I know,
and have known since the day I first used it (let's see, must have been
on Sixth Edition in 1979) that "tr" is a plain _character-oriented_
command. It is not a text tool, it is a character tool. I know
you know that. What I am telling you is that I always knew it.
There was not the slightest bit of `luck' involved. If your tr
needs a terminal newline, your tr is busted, end of discussion.
)
OK,
John.
next prev parent reply other threads:[~1993-06-05 13:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-06-05 12:53 malte
1993-06-05 12:55 ` John Mackin [this message]
[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=199306052255.25518.rc.bakay@civil.su.oz.au \
--to=john@civil.su.oz.au \
--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).