On 4/26/2012 7:40 AM, Eric Blake wrote:
On 04/26/2012 08:13 AM, Andrew DeFaria wrote:
I remember that Cygwin used to not be able to run scripts that were
converted or were in "DOS" mode - had trailing carriage returns in the
file. It would fail because the #! line might have /bin/bash\r which wa
Earnie Boyd sent the following at Thursday, April 26, 2012 10:27 AM
>
>http://cygwin.com/faq/#faq.api.cr-lf
You can also avoid to change the source code at all
^
changing
- Barry
Disclaimer: Statements made herein are not made on behalf of NIAID.
On 04/26/2012 08:13 AM, Andrew DeFaria wrote:
> I remember that Cygwin used to not be able to run scripts that were
> converted or were in "DOS" mode - had trailing carriage returns in the
> file. It would fail because the #! line might have /bin/bash\r which was
> not a file (bash with a carriage
On 04/26/2012 07:26 AM, Earnie Boyd wrote:
On Thu, Apr 26, 2012 at 10:13 AM, Andrew DeFaria wrote:
I remember that Cygwin used to not be able to run scripts that were
converted or were in "DOS" mode - had trailing carriage returns in the file.
It would fail because the #! line might have /bin/ba
On Thu, Apr 26, 2012 at 10:13 AM, Andrew DeFaria wrote:
> I remember that Cygwin used to not be able to run scripts that were
> converted or were in "DOS" mode - had trailing carriage returns in the file.
> It would fail because the #! line might have /bin/bash\r which was not a
> file (bash with a
I remember that Cygwin used to not be able to run scripts that were
converted or were in "DOS" mode - had trailing carriage returns in the
file. It would fail because the #! line might have /bin/bash\r which was
not a file (bash with a carriage return that is). But the behavior has
changed. Now
6 matches
Mail list logo
