You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting the editor setting when using openEditor to code-insiders 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 code-insiders binary to insiders then using insiders 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 /usr/local/bin/code-insiders
still opens the file with visual studio code, maybe it gets confused just because the binary starts with code-?
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.
The text was updated successfully, but these errors were encountered:
Setting the editor setting when using
openEditor
tocode-insiders
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 thecode-insiders
binary toinsiders
then usinginsiders
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
/usr/local/bin/code-insiders
still opens the file with visual studio code, maybe it gets confused just because the binary starts with
code-
?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.
The text was updated successfully, but these errors were encountered: