env-editor

Setting the editor setting when using to which is the default binary that is linked when installing insiders, still uses vscode to open the file. A simple workaround for this is to symlink the binary to then using as the binary option to open the file. This seems to be some conflict in the code, when trying to resolve the editor, as using a direct path still opens the file with visual studio code, maybe it gets confused just because the binary starts with ? Happy to make a PR to fix this and add support for insiders when I get some time, just wanted to check this with you first 🙂 Thank you for your work.

I'm using Ubuntu 17.10. Running vim on the terminal issues . Instead vim runs by inputing the vi command. I don't know if this is a special default for Ubuntu. I haven't personally changed anything in my environment that would make vim not be a command.

My personal preference is VSCodium, the "Free/Libre Open Source Software Binaries of VS Code" as stated on the home page. I just added it to the list of available editors. As I am not using a Mac I could not test the "path", but I think it is the correct one.