Paul Cochrane wrote:
Do users on Windows have major problems editing the
files because they're all (mostly) UNIX line endings?
Yes. Even things I may use that can handle input with UNIX line endings,
tend to spit out files with Windows line endings too. I rely on
eol-style being set to native for this all to work out, and when I edit
files without it set someone probably make an "OH NO \r's everywhere"
kinda comment in my direction. :-)
Should we
change the coding standard test to look just for text files with the
eol-style set to native, and not worry about DOS/UNIX etc line
endings?
I think native should just do the right thing and be set on almost every
file - many files are set with this property already.
If you're checking out on a UNIX platform and seeing things with a
DOS/Windows line ending, that's probably an issue (a few select test
files aside, I guess). But on a DOS/Windows platform, it should be the
common case and it's the UNIX endings that are the problem. Both of
these point to forgetting to set eol-style to native.
Thanks,
Jonathan
