-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
BUG: VSCode doesn't remember the custom profile I selected with right-click "Open with Code" #214019
Comments
You may like this, which is available in Insiders and will arrive generally when 1.90 ships toward the end of next week. |
hey again @gjsjohnmurray, I noticed that the mentioned function here was working after one of the recent updates(I believe after the 1.9 like you said), but it seems to be gone/broken again. Selecting an imported custom profile does not stick when closing and reopening the app. |
What value did you pick for the setting described in https://code.visualstudio.com/updates/v1_90#_configure-custom-profile-for-new-window? |
Does this happen only when you open the folder in above way? Or also when you open the folder from VS Code? |
yep I definitely missed that... (-_-"). Everything's working perfectly now, thanks again @gjsjohnmurray !! |
Hey @sandy081, this issue might need further attention. @codewizard13, you can help us out by closing this issue if the problem no longer exists, or adding more information. |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
Sorry, it's been a busy month! I just caught this - I'm testing whether the window.newWindowProfile sticks correctly. I will make a note to report back next week! :) |
Hey, sorry - I just saw your comment! Thanks for the link - this update looks like EXACTLY what I'm asking for. As long as it works when I right-click (context menu) in windows and chose "Open with Code". |
Confirming: This works! :) Thanks! |
Type: Bug
VS Code version: Code 1.89.1 (dc96b83, 2024-05-07T05:13:33.891Z)
OS version: Windows_NT x64 10.0.22631
Modes:
Further Details:
Challenges with Ambiguous Terminology
I perceive there may be a problem using the term "default" among the dev team. Perhaps there is confusion over what is meant by "default" in the ticketing system among the developers on VSCode and that makes it hard to even pose an understandable question. What do I mean?
Well, some devs may hear "default profile" and think that means "the included core profile used if no custom profiles have been created or selected". But, other devs will think it means "the profile that VSCode always boots into, no matter what", as in, when I right-click and choose "Open with Code" from the context menu, or open VSCode any other way, it should boot into this profile by default.
Clearly, these are two different meanings of "default" and I suspect devs are conflating the two. The last meaning is the least desirable and least user-friendly.
Perhaps a different term besides default should be used in the UI and internal ticketing system? Here is one possibility:
I suspect this what many users think when they see the "default profile" option.
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
Extensions (54)
(1 theme extensions excluded)
A/B Experiments
The text was updated successfully, but these errors were encountered: