Mihai Popescu
Mihai Popescu
The package is not listed because it was removed from Alcatraz https://github.com/alcatraz/alcatraz-packages/issues/593. The complaint was that the package was dependent on CMake but I can't see how.
Oh ok. Now I see. Maybe `editorconfig-core` can be distributed as a precompiled library.
As a workaround you can fork that repo and revert the commit or faster if you use an existing fork that doesn't have that commit. Go to: _Package Manager_ ->...
@viskin It's probably related to this: > The problem is that on a standard OS X install these do not build (cmake: command not found), so from an Alcatraz point...
We use are using it at Unity. I'm glad you reacted so quickly and there is a release plan.
Any updates on this?
This issue is still present. +1
I'd adhere also to a way to disable VS2017 "native" support (or for Microsoft just to fix it) and put the extension back on the marketplace. We're waiting for `utf-8`...
really? for any type of file? are you sure it's not your repo setting who is messing with eol's?
Then let's just close the issue. It's a Vistual Studio issue and we should open it on their side.