mirror of
https://github.com/Microsoft/vscode
synced 2024-09-18 01:58:27 +00:00
c536595a7f
The standalone CLI should detect and fall back to using and system-installed VS Code instance, rather than trying to download zips and manage its own VS Code instances. There are three approaches used for discovery: - On Windows, we can easily and quickly read the register to find installed versions based on their app ID. - On macOS, we initially look in `/Applications` and fall back to the slow `system_profiler` command to list app .app's if that fails. - On Linux, we just look in the PATH. I believe all Linux installers (snap, dep, rpm) automatically add VS Code to the user's PATH. Failing this, the user can also manually specify their installation dir, using the command `code version use stable --install-dir /path/to/vscode`. Fixes #164159 |
||
---|---|---|
.. | ||
azure-pipelines | ||
builtin | ||
darwin | ||
lib | ||
linux | ||
monaco | ||
npm | ||
win32 | ||
.cachesalt | ||
.gitattributes | ||
.gitignore | ||
.moduleignore | ||
.webignore | ||
eslint.js | ||
filters.js | ||
gulpfile.compile.js | ||
gulpfile.editor.js | ||
gulpfile.extensions.js | ||
gulpfile.hygiene.js | ||
gulpfile.js | ||
gulpfile.reh.js | ||
gulpfile.scan.js | ||
gulpfile.vscode.js | ||
gulpfile.vscode.linux.js | ||
gulpfile.vscode.web.js | ||
gulpfile.vscode.win32.js | ||
hygiene.js | ||
package.json | ||
tsconfig.build.json | ||
tsconfig.json | ||
yarn.lock |