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

From: Wilbert van Dolleweerd <wilbert@arentheym.com>
Date: May 6, 2010, 07:29 UTC
Message-ID: <o2ved79be1d1005060029n67f451c6p3b48b83c51031222@mail.gmail.com>
In-Reply-To: <x2h600158c31005051935i6f379a9j6aa36b4503776b87@mail.gmail.com>

Show 7 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....)

-- 
Kind regards,

Wilbert van Dolleweerd
Blog: http://walkingthestack.blogspot.com/
Twitter: http://www.twitter.com/wvandolleweerd

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.