On Thursday 12 June 2008, Les Mikesell wrote: >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 write it back out. >> >> Plus, you probably have a program called dos2unix installed... > >Oops, I should have read past the word 'legacy' which must not have >meant what I thought. >tr '\r' '\n' >should work. It did Mike, thanks. Legacy in this case is a TRS-80 Color Computer 3, now old enough to buy a drink in any state of the union. The OS was originally OS-9, but we've been working on it, so its quite a bit faster than the original. -- 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) The state of some commercial Un*x is more unsecure than any Linux box without a root password... -- Bernd Eckenfels -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
