How to determine which VSCode extensions were installed by default? - visual-studio-code

I'm trying to "reset" my VSCode configuration as it pertains to Java without having to reinstall VSCode entirely, so I am wondering how to determine which plugins were default (installed at VSCode install time) and which were installed by me?
I have tried:
Determining the date of installation of the extensions (but I can't find it).
Using some kind of sort by/show only defaults feature (doesn't seem to exist).

Related

How to tell VsCodium and VsCode apart?

Without having done the installation myself, is there an easy way to check (maybe from within the application) if it is VsCode or VsCodium?

Why cannot I use the Vim VSCode extension over ssh or wsl?

I cannot install the Vim VSCode extension on my headless machine through VSCode remote development nor in WSL. I think I used to be able to but I uninstalled it once and since then I haven't been able to install it again. I can only install and uninstall on my Windows computer but not remotely: when I click the button to install Windows extensions to server, the Vim VSCode extension is not part of the batch:
Edit: actually the extension stopped working in Windows as well without obvious reason.
Here is a list of my extensions: maybe I introduced incompatibilities I am not aware of:
I wonder how to get a JSON list of the extensions by the way :(
I might be wrong but I don't believe the normal VSCodeVim extension requires Vim itself to be installed as it just emulates it, so it shouldn't need installed in the remote environment as long as it is installed/enabled which it looks to be. Is it not working?
There was a bug in the settings JSON file. There was some syntax error, possibly caused by the installation of some other extension.

VSCode: How to fix Python extension version for Python 2 compatibility and prevent automatic upgrade?

I have a legacy code using Python 2. The last version of VSCode Python extension that supports Python 2 is v2022.2.1924087327
It is very easy to change the extension to an older version.
My problem is that VSCode always automatically updates the extension. Since I'm using it in a remote machine, when I loose connection, it automatically updates the extension, and I must manually downgrade it, reload the window and start it again.
Is it possible to fiz the version of my Python extension in VSCode?
I've just found how to prevent extensions to automatically upgrade.
And I just set:
{
"extensions.autoUpdate": false
}
It will now ask me for each extension upgrade, it is an annoyance, but at least I can control it.
If someone finds how to disable auto update just for the Python extension, I'll mark it as the correct answer.

How to configure VSCode to find a third-party tool (e.g. stack, yamllint) if these tools are installed through anaconda?

Assuming that VSCode is installed and an anaconda environment is setup. The default conda environment contains language analysis and compilation tools like stack (for haskell) and yamllint (for yaml). However, since conda 3.4 they are under <conda_install_dir>/bin, which is not included in system PATH environment variables. The only executable is conda itself.
After installation of VSCode and its plugin, I frequently encounter error messages indicating that executables of these tools are not found. E.g. for stack, the message is:
Project requires Cabal but it isn't installed
It appears that the only way to make it work is to override the PATH variable in VSCode to make it different from the one used by OS. Is there a option to allow this overriding?
Thanks a lot for your help
have you tried updating your PATH to simply include it ?

Custom node version to run VSCode extensions

I'm making a vscode extension for my personal use. I'd really like to use a more recent node version. However, I'm not sure how does VSCode chooses which node version to use.
The only node.js that I have installed is 8.1.3. But when I debug the extension, I see that VSCode uses 7.*.* (via process.version).
I've been searching documentation for an hour, so far, without luck. Any help is appreciated.
This is not possible. Quoting the reply of one of the team members (Andre Weinand) in #18253:
VS Code runs extensions on the node version that is built into electron (on which VS Code is based). This cannot be changed.