-
Notifications
You must be signed in to change notification settings - Fork 308
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
Standardize windowing behavior from Remote Explorer view #8397
Comments
cc for feedback: @bamurtaugh @aeschli @chrmarti @connor4312 @eleanorjboyd @roblourens |
Thanks so much for putting this together @joyceerhl!
I like this option to help avoid limiting users to just one path. |
We also have the setting Also I don't think it's an issue if alt in the open recent picker works differently than an alt-action on a menu button, to me they are different things. I'm fine with 1 or with 2. If it's 1, then both options should show up in the context menu too |
Same with WSL. The |
@aeschli when I have |
I think for SSH it makes sense that you do not currently observe |
Moving this out to May so I can get input from all remote owners on this issue. |
Here's a related issue on this topic: #8356 |
Ok you are right, I didn't realize that. On the distro item, it's currently a I'm not a big fan of the setting ( |
I'd suggest that we offer both options (open in current window, open in new window) for the remote explorer (inline as well as context menu), as I wouldn't want to take away functionality for the remotes which already offer the ability to do both. What do you think @aeschli? |
That's what Remote-SSH currently does which I like for being very clear. It does take some space, but I think it's still a good trade-off as a user setting can't cover that you don't always want the same behavior and the modifier keys tend to be too subtle for new users. (Consistency with modifier keys where we support them would still make sense though.) |
Sounds good. So to summarise, for the remote explorer context menu we add two commands that are explicit, and we do not use the |
agreed that I think we should maintain both options (open in current window, open in new window) so this sounds good to me. Thanks! |
Closing this issue as it looks like Containers, WSL and Remote Repos have updated windowing behavior in the remote explorer and SSH/Tunnels has no changes required. Thank you everyone! |
Part of microsoft/vscode#178854
All remotes which contribute views to the remote explorer currently offer different ways to open a remote in a current or new window. Ideally we would offer the same options across all our remotes to reduce hesitation when choosing to open a remote.
Proposal:
Suggestion 1: Offer one inline action and use alt modifiers, this is done by setting a command ID in the
alt
property for a command contributed toview/item/context
(only Remote Repos does this today):Suggestion 2: Offer two inline actions (one for opening in current and another for opening new window)
Suggestion 3: Only offer one option (open in current or open in new window)
$(window)
for current window,$(empty-window)
for new windowThe text was updated successfully, but these errors were encountered: