Fix line-endings (only ws changes)

[cdunn2001]

No actual diffs. (git diff -w)

This PR is not a real change, so it can be merged immediately. That would help my rebasing for future PRs.

(If the repo has only \n line-endings, then people can get whatever they want by setting their .gitconfig properly.)

[cdunn2001]

You can choose "Files changed", then click the gear drop-down, select "hide whitespace changes", and "Apply". There are no actual diffs here.

[cdunn2001]

microsoft/WSL#184

[cdunn2001]

With crlf endings, it's easy to get into a state on OSX where git status always says dirty, and it's surprisingly difficult to get out of that state. (I had to alter .gitattributes in a non-obvious way.)

[Araq]

Ok, but the downside is that we do not test CR-LF line endings anymore.

[cdunn2001]

The .gitattributes file definitely helps, since it will prevent existing files from regressing. I think we need * text=auto eof=lf though. I'll add that to a PR.

• https://stackoverflow.com/questions/9976986/force-lf-eol-in-git-repo-and-working-copy

I could also add a test for line-endings.

I was thinking of switching from TravisCI to github CI, which I learned about recently from cblake's cligen Nim library. Interested? I was surprised to learn that forks actually run the same tests, which is both good and bad. It's good if the tests are fast and stable.

[Araq]

Github CI? Sure, bring it on please.

[cdunn2001]

On second thought, it might be hard to beat the caching of TravisCI, though GitHub has some caching too.

c-blake used this: https://github.com/jiro4989/setup-nim-action/blob/v1/action.yml

which uses these javascripts: https://github.com/jiro4989/setup-nim-action/blob/v1/lib/

That looks unmaintainably complicated, so I'll punt. But jiro4989 did some really nice work here.

https://github.com/jiro4989/setup-nim-action