Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question on default profile behaviour with extensions and settings #1

Open
jonnyhotchkiss opened this issue Dec 5, 2023 · 0 comments

Comments

@jonnyhotchkiss
Copy link

jonnyhotchkiss commented Dec 5, 2023

Hi I'm tinkering with vscode to try make it look and behave as I expect, looking at things like status bar and extension powerups to yield more information about settings (to understand why keyboard shortcuts aren't firing, and definitions of other when contexts like hasChatProvider)

I've added a vs-code dev profile, for testing vscode extensions like multicommand, command-statusbar, and perhaps this extension.

I notice that on install extensions are 'global' , but when I switch profiles the extensions don't appear to be installed, but you mention default behaviour is extensions are managed at user and workspace level. For the record I'm also using a portable install, to monitor settings changes in the data directory of the portable install.

(Tangent but you may know) I see the profile folders have names like -66fd11a4 - can these be changed? I don't see how these are referenced (I tried adding the vscode directory as a folder in vscode then searching in that for instances of -66fd11a4, but no references seen.

EDIT: a question! How does vscode manage extensions normally (in portable mode, if different - I notice no workspace settings, for example, in case that's one factor), and what are the advantages + disadvantages of using this extension ?
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant