fix vscode 1.29.0's breaking feature: eol=auto

[gfx]

Fix #65

workaround before this PR

Set files.eol to "\n" or "\r\n" in vscode settings. auto is a new feture introduced in v1.29.0

[gfx]

I think it should come from the current document 🤔

[fedulovivan]

Right, should be better taken either from current document, or probably vscode provides some API to resolve auto to os-specific value.

[3ygun]

@gfx wanted to link the original VSCode changes

• Ticket that purposed the change Introduce new default auto for files.eol  microsoft/vscode#60955
• Link to the commit that changed everything for us 😡

Don't know if you can call one of those getEol methods and/or import OS and do the check yourself

[ctsstc]

Now seeing that #72 looks to be a duplicate of this, although a slightly different implementation.

[ctsstc]

From #72 (review)

Seems that the VSCode snippet builder builds snippets the same way via an array and then joins them together. It seems they are only using '\n' for all cases. Maybe the secret is to just do \n and post processing will handle the rest.

VSCode's snippet building:
https://github.com/Microsoft/vscode/blob/82863aac3b43b9559057295afcf5f99edd9f5f22/src/vs/workbench/parts/snippets/electron-browser/snippetsFile.ts#L227

VSCode's snippet implementation example:
https://code.visualstudio.com/docs/editor/userdefinedsnippets#_global-snippets

I dug around in the VSCode Extension API and couldn't really find anything about determining the OS EOL's value.

Looks like we should be able to use require('os').EOL though.

[JedBartlett]

Should this be closed then to let #72 go through?

[gfx]

Closed in favor of #80