Re: What should be the CRLF policy when win + Linux?

From: hasen j <hasan.aljudy@gmail.com>
Date: May 6, 2010, 15:34 UTC
Message-ID: <i2i600158c31005060834s72e10fb7te19048e3b174d29b@mail.gmail.com>
In-Reply-To: <o2ved79be1d1005060029n67f451c6p3b48b83c51031222@mail.gmail.com>

On 6 May 2010 01:29, Wilbert van Dolleweerd <wilbert@arentheym.com> wrote:

Show 14 quoted lines

>> I personally find that autocrlf causes more confusion than it solves problems.
>>
>> I've yet to see a text editor on windows that can't handle \n line
>> endings. (Notepad doesn't count)
>>
>> Just keep the project with \n line endings, disable autocrlf, and make
>> sure that people are aware of this.
>
> Editors may handle it gracefully but older Windows programs will have problems.
>
> For instance, Visual Studio 6 will barf on Visual Basic projectfiles
> with non-windows line-style endings. (And please don't ask why I know
> this....)
>

Well, this is the exception that proves the rule then :)

Anyway, If it's a VB project, might as well just keep the files with CRLF endings then.

I don't know all linux editors, but I've yet to see one that can't handle CRLF endings.