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

Re: tr problem



On Thursday 12 June 2008, Les Mikesell wrote:
>Gene Heskett wrote:
>> 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?"
>>
>> Or is there a better tool for this than tr?
>
>The tr syntax would be
>tr -d '\r'
>but for one or a few files you can just load in vi (vim) and
>
>:set fileformat=unix

And that might be something that is not in the vim manpages Mike, thanks.

>and write it back out.
>
>Plus, you probably have a program called dos2unix installed...

That is the other option & with my CRS, I couldn't remember that name with a 
$1000 bill being offered.  I'm seemingly being reminded that memory is the 
second thing to go. :)

>--
>   Les Mikesell
>    lesmikesell gmail com



-- 
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)
Hello?  Enema Bondage?  I'm calling because I want to be happy, I guess ...


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