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
I'd love to be able to install Emacs, VIM, and SublimeText bindings into the standard image and make it possible for users to choose which extensions are enabled. I don't believe this is possible wholly through a settings.json setting, but we can see. It might require a more custom hack to read a list of active extensions from a different secret, and modify the local .vscode settings as needed to enable/disable.
The text was updated successfully, but these errors were encountered:
Would "recommended extensions" be appropriate? I need to see if we can pre-download the extensions without installing them. When the editor comes up VSCode will pop-up that there are recommended extensions. The user can then decide how to proceed.
Separately there can be a way for a user to supply a list of extensions in a secret to be installed in start_vscode.sh. Or would the secret be the preferred way?
I'd love to be able to install Emacs, VIM, and SublimeText bindings into the standard image and make it possible for users to choose which extensions are enabled. I don't believe this is possible wholly through a
settings.json
setting, but we can see. It might require a more custom hack to read a list of active extensions from a different secret, and modify the local .vscode settings as needed to enable/disable.The text was updated successfully, but these errors were encountered: