[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cygwin
Subject:    Re: Bash 3.1.17(8): Scripts on textmode mount get problems with CR    characters
From:       Matthew Woehlke <mwoehlke () tibco ! com>
Date:       2006-10-27 20:14:07
Message-ID: ehtpaf$v3c$1 () sea ! gmane ! org
[Download RAW message or body]

Buchbinder, Barry (NIH/NIAID) [E] wrote:
> on Friday, October 27, 2006 2:16 PM, Matthew Woehlke wrote:
>> Long, Phillip GOSS wrote:
>>> U don't have d2u on all platforms, but U probably _do_ have awk or
>>> gawk on every platform.  I came up with a simple fix for the CRLF
>>> problem when I encountered it, which is still klugy, but works on
>>> every POSIX or Cygwin platform:
>>>    gawk '//' fileFromTextMount > fileWithLFOnlyOnBinMount
>> ...or:
>> $ cat <file> | tr -d '\r'
> 
> Save a cat:
> 	$ tr -d '\r' < <file> 

d'oh, right :-)

> or, if you might have other "\r"s in the file,
> 
> 	$ sed -e 's/\r$//' <file> 
> 
> Actually, just running something through sed seems to do it for me on a
> bin mount (though maybe this is just the same as running something
> through gawk).

I believe this works because *some* (not all IIRC) versions of sed read 
in text mode by default. The point of my original post, however, was 
that I am guessing that 'tr' is faster than sed/awk.

-- 
Matthew
"Two IIRC's must make a right" -- Larry Hall (paraphrased)


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

[prev in list] [next in list] [prev in thread] [next in thread]