Connor Peet c536595a7f cli: fallback to system installs in the standalone CLI ... 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		2022-10-20 10:54:13 -07:00
..
src	cli: fallback to system installs in the standalone CLI	2022-10-20 10:54:13 -07:00
build.rs	cli: use hard tabs to align with vscode style	2022-09-23 14:17:01 -07:00
Cargo.lock	cli: fallback to system installs in the standalone CLI	2022-10-20 10:54:13 -07:00
Cargo.toml	cli: fallback to system installs in the standalone CLI	2022-10-20 10:54:13 -07:00
CONTRIBUTING.md	cli: point docs to the new RA extension ns (#162500)	2022-10-04 08:17:10 -07:00
rustfmt.toml	cli: use hard tabs to align with vscode style	2022-09-23 14:17:01 -07:00