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 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