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
{{ message }}
This repository has been archived by the owner on Jul 18, 2022. It is now read-only.
The extension checks if it runs in VSCode/VSCode insiders/VSCodium by checking the name of its binary. This is not a reliable way to detect the Code branding used.
For example, in my case, process.execPath is just /usr/lib/electron11/electron.
Furthermore, the editor is launched with /usr/bin/code, which is a symlink to /usr/bin/code-oss.
A better way would to check this would be to test vscode.env.appName for Code - OSS or VSCodium, etc..
The text was updated successfully, but these errors were encountered:
dithpri
changed the title
Relying on the binary name incorrectly detects vscode version
Relying on process.execPath name incorrectly detects vscode version
May 5, 2021
dithpri
changed the title
Relying on process.execPath name incorrectly detects vscode version
Relying on process.execPath incorrectly detects vscode version
May 5, 2021
The extension checks if it runs in VSCode/VSCode insiders/VSCodium by checking the name of its binary. This is not a reliable way to detect the Code branding used.
For example, in my case,
process.execPath
is just/usr/lib/electron11/electron
.Furthermore, the editor is launched with
/usr/bin/code
, which is a symlink to/usr/bin/code-oss
.A better way would to check this would be to test
vscode.env.appName
forCode - OSS
orVSCodium
, etc..Related: #42 #12
The text was updated successfully, but these errors were encountered: