-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
programming profile quick switcher is gone #227872
Comments
It was removed because once a profile is associated to a workspace, switching profiles is not a common action. So, one can use the new profiles editor or the command (command pallette) to switch profiles. User Docs - https://code.visualstudio.com/docs/editor/profiles#_switch-profiles |
For me, switching profiles in a workspace was a common action. I work with monorepos and multiple customers where each customer has their own monorepo. I would reuse the profiles across monorepos for activities that are the same in each monorepo. So e.g. for customers with markdown documentation I have a markdown profile when editing this documentation. For monorepos that contain C# code, I would then switch to the C# profile to work on that. I hope this will be reconsidered and at least a setting is provided to bring back the profile quick switcher. |
Reopening this to consider it for discussion |
Same issue here (as mentioned in duplicate #228944 )! I use VS Code for my research and switch between two profiles: one for coding tasks and another for LaTeX work (with a lighter theme, fewer or different extensions, etc.). Whenever I generate new results or need to update the Methods section of my paper after adjusting the code, I quickly switch profiles, navigate to my open LaTeX file, make the necessary changes, and then switch back to my coding profile. While it's not a huge deal to work with the new profile editor, I can see how things could get quite messy with multiple profiles. Also, I’m not entirely sure why a profile is now linked to a workspace. Isn’t the point of workspace settings to differentiate between various workspaces, while profiles are intended for different "users" working within the same workspace? |
I didn't even notice it is tied to a workspace. I used the feature without workspaces except one. |
I think that switching profiles is more common than managing profiles. Thus, I'd also go back to this situation: Maybe we can rename "Profiles" to "Manage Profiles..." FYI @isidorn |
I like @hediet suggestion to use "Manage Profiles", I would not use the Ideally if there is just the default profile, this would not be a submenu, but just one action. And it turns into a submenu once there are 2+ profiles. Btw Outlook also calls it Manage Profiles |
I also use multiple profiles in a monorepo with many different file types, with different VSCode extensions per type - multiple programming languages, shell scripts, documentation files, etc., but I use the profiles as a way to reduce malware risk from a 3rd party extension downloading/running arbitrary binaries - by only having the needed extensions enabled for the current file type, I figure that gives more of a chance for Microsoft to catch an extension update that introduces malware before I have that specific extension enabled again. (Other items like adding extension permissions/sandboxing #52116 or the not-planned auto-switch-profile-based-on-language #174211 would also help, but in the absence of those, manual profile switching seems like the best chance to reduce the risk of extensions downloading/running arbitrary binaries on my system, presuming we aren't avoiding 3rd party extensions entirely), so profile switching is a common action for me and restoring fast access would be nice. |
Also, at present in the command palette, "Profiles: Open ___ Profile" is a top-level command which opens the profile in a new window, but "Profiles: Switch Profile" is a multi-step command (with the specific command selected (after "Switch Profile" is selected) which opens the profile in the current window. I more commonly switch profiles for the current window, not a new window, so my preference would be to reverse the one-step/multi-step commands, although I don't know which is more common for others. |
I frequently open folders on disk in vscode to peruse and/or edit files. Maybe Python, maybe JS, maybe R, maybe something else. It was extremely handy to be able to quickly select the right profile for that folder. I strongly encourage you to bring this back. While it's not hard, per se, to switch via the command palette, sometimes you're just feeling, well, mousey, and don't want to move your hands over to the keyboard. Besides, there's such a thing as too much minimalism. |
@FH-Inway love your profiles! I can only imagine what is "Code Crime Scene" 😆 |
Does this issue occur when all extensions are disabled?: Yes/No (don't know - the point of profiles for me is to switch between different configurations of extensions which are exclusive to each other in the profiles)
Steps to Reproduce:
This was awesome. I could just change it without another dialog opening. Would be great to have it back.
The text was updated successfully, but these errors were encountered: