From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mod.civil.su.OZ.AU ([129.78.142.6]) by hawkwind.utcs.toronto.edu with SMTP id <2759>; Sat, 5 Jun 1993 09:03:46 -0400 Received: by mod.civil.su.oz.au id <28693>; Sat, 5 Jun 1993 23:03:19 +1000 From: John (Most modern computers would break if you stood on them) Mackin Date: Sat, 5 Jun 1993 08:55:54 -0400 To: rc@hawkwind.utcs.toronto.edu Subject: Re: here strings In-Reply-To: <9306051253.AA09468@idefix.techfak.uni-bielefeld.de> Message-ID: <199306052255.25518.rc.bakay@civil.su.oz.au> X-Face: 39seV7n\`#asqOFdx#oj/Uz*lseO_1n9n7rQS;~ve\e`&Z},nU1+>0X^>mg&M.^X$[ez>{F k5[Ah<7xBWF-@-ru?& @4K4-b`ydd^`(n%Z{ [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.