[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: tr problem

On Thursday 12 June 2008, Michael Schwendt wrote:
>On Thu, 12 Jun 2008 16:35:09 -0400, Gene Heskett wrote:
>> Hi folks;
>> I'm trying to convert a test file, src code for a legacy computer, whose
>> eol is a single cr into one with a newline subbed for each cr, and tr is
>> being a pita, it broken, or there is PEBKAC.
>> If I use this syntax:
>> tr -c \r \n <filename  >filename2
>> Then the whole file is converted to nnnnnnnnnn's, every byte.
>> The manpage (and pinfo tr too) is, shall we say, completely lacking in how
>> to handle the file I/O.
>> So how do you use tr?"
>Why option -c?
>tr '\r' '\n' <filename  >filename2
>would do it.

Cuz the manpage says that it triggers the character convert thing?

It doesn't touch on its performance if the option isn't given.  And it doesn't 
mention using the quotes either, but it worked just fine, thank you very much.

Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Cabbage, n.:
	A familiar kitchen-garden vegetable about as large and wise as
	a man's head.
		-- Ambrose Bierce, "The Devil's Dictionary"

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]