Issue Type: Feature Request
Can't save workspace locally when using remote extension, and connected remotely.
The feature used is "File>Save Workspace as..."
This used to work, but it doesn't seem to work anymore. All that shows up is directories remotely.
VS Code version: Code 1.50.1 (d2e414d9e4239a252d1ab117bd7067f125afd80a, 2020-10-13T14:53:05.704Z)
OS version: Darwin x64 19.6.0
Remote OS version: Linux x64 4.18.0-193.6.3.el8_2.x86_64
(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:
I also heavily rely on this feature, can you add it back?
The workaround is to store the workspace on remote and opening it from the local side either from the recent menu or by using the command line:
code --remote ssh+remotetaddr /home/you/workspacefile.code-workspace
The workaround is to store the workspace on remote and opening it from the local side either from the recent menu or by using the command line:
code --remote ssh+remotetaddr /home/you/workspacefile.code-workspace
But it is not convenient to do so as I have to memory or store this command somewhere, also it helps to some extent, VScode save locally is better.
Is the workaround is the only way for this issue? I don't understand why not allow the remote folder to local workspace.
Roll back to vscode 1.49.3 is a good choice to me.
@aeschli I feel it is senseless that we have to disable the entire feature because of a minor issue. Many projects of mine and my clients and people around here too were reliant on the feature because of convenience. Maybe enable the feature and warn the users for the encoding issue and provide a workaround for it instead of disallowing local workspace saving. This is like instead of fixing the hinge you are removing the entire door. pretty senseless imo.
I added it back.
I added it back.
Thanks so much!
Most helpful comment
I also heavily rely on this feature, can you add it back?