bug-bash
[Top][All Lists]
Advanced

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

Re: Error when script uses CRLF line endings w/ if stmt


From: Marc Herbert
Subject: Re: Error when script uses CRLF line endings w/ if stmt
Date: Fri, 05 Feb 2010 16:10:18 +0000
User-agent: Thunderbird 2.0.0.23 (X11/20090825)

Jan Schampera a écrit :

> Moreover, POSIX talks about "<newline>" here, which is a \n. Though I
> didn't read through all the rationales, I just took a quick look, maybe
> it's not limited to \n.

'\n' can be two characters outside of POSIX, see "man fopen".

             -----

It would feel good to use CRLF to bash Windows once again. Isn't
ridiculous and painful to have two characters for only one thing?

Unfortunately CRLF pre-dates Windows by decades. You can argue it is
older and more standard than LF. For instance many internet protocols
use it.

Now I wonder how come a third convention emerged. Just to "think different"?






reply via email to

[Prev in Thread] Current Thread [Next in Thread]