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

On Thu, 6 May 2010, hasen j wrote:

A _lot_ of UNIX editors will handle CRLF endings, but if you change a file, they often write the result back with _mixed_ endings. Some will also show the CR as '^M' or some other garbage at the end.

A number of tools will also end up confused, including very fundamental things like "grep". Try this:

	echo -e "Hello\015" > f
	grep 'Hello$' f

and notice how the grep does _not_ find the Hello at the end of the line, because grep sees another random character there (this might be unportable, I could easily imagine some versions of grep finding it).

So I would strongly suggest against CRLF on UNIX. It really doesn't work very well, even if some tools will handle it to some limited degree.

In short: having 'core.autocrlf' set will likely make it much more pleasant to work across different platforms.

			Linus