Allow running a setup script on Windows analogous to setup.sh on Linux

[E14]

Script is located at %APPDATA%/elixir_ls/setup.bat which usually translates to C:\Users\<username>\AppData\Roaming\elixir_ls

Example use-case:

@echo off
CALL "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat"

Very useful for nifs.

[axelson]

Thanks! This does indeed look helpful ❤️

[princemaple]

FYI if anyone fails to start elixir-ls after adding a setup script, make sure the script does not print anything.

@echo off
CALL "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Auxiliary\Build\vcvarsall.bat" x86_amd64 >nul

@echo off does not prevent the results from being printed, only the commands. >nul is needed too.

[axelson]

@princemaple thanks for the note. I think it would be helpful for more people to see it so I've added a similar note to the README: #468

Does the wording on that make sense to you?

[princemaple]

It looks good to me. I'm not a batch script expert though, I'm not sure if it is needed on every single line. I guess to be safe - sure. 👍 Thanks

[E14]

@princemaple thanks for the note. I think it would be helpful for more people to see it so I've added a similar note to the README: #468

Does the wording on that make sense to you?

We could update the batch file to add > nul to the calls in debugger.bat and language_server.bat directly, that should prevent the output of stdout at least - I think (not a batch expert either), maybe @princemaple can test this with their existing script?

[princemaple]

@E14 good thinking. Adding >nul at the end of the line with the call seems to do the trick.

[princemaple]

CALL "%APPDATA%\elixir_ls\setup.bat" > nul 2>&1 If the user can make sure the script works before really using it.