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, whic
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
>>
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 > fileWit
-Original Message-
>From: Eric Blake
>Sent: Wednesday, October 25, 2006 8:05 AM
>To: Bruun, Peter Michael
>Subject: Re: Bash 3.1.17(8): Scripts on textmode mount get problems
with CR characters
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>http://c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://cygwin.com/acronyms/#PPIOSPE - redirecting to the list.
According to Bruun, Peter Michael (HP C&I CME OSS CoE) on 10/25/2006 1:18 AM:
> Hello Eric,
>
> Thanks for the thorough explanation.
>
> Yes, the missing handling of CRLF in `` and $() i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://cygwin.com/acronyms/#PPIOSPE - forwarding to the list accordingly.
> -Original Message-
> From: cygwin-owner AT cygwin DOT com
^
http://cygwin.com/acronyms/#PCYMTNQREAIYR - munged accordingly.
http://
On 10 October 2006 16:02, Bruun, Peter Michael (HP C&I CME OSS CoE) wrote:
> It has been one of the main strengths of Cygwin tools, that all of them
> understood this.
That is not and never has been true. The cygwin tools are standard unix
code and they only understand LFs. The cygwin dll gen
Bruun, Peter Michael (HP C&I CME OSS CoE hp.com>
writes:
>
> With release 3.1.8 of Bash, however, it no longer understands Windows
> conventions.
>
> I get:
>
> Bash is broken in /home/pmb
> Bash is broken in C:/Temp
> Bash works in /tmp
>
>
> Or have I overlooked something?
You overlooked
For various reasons (like various revision control systems), as
described by others elsewhere, some of us prefer to follow the Windows
standard of text file lines ending in CRLF when working on windows.
It has been one of the main strengths of Cygwin tools, that all of them
understood this.
With
9 matches
Mail list logo