You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To pick up a draggable item, press the space bar.
While dragging, use the arrow keys to move the item.
Press space again to drop the item in its new position, or press escape to cancel.
In case this issue is about fixing the remote extensions to work with code-server, this related issue can be closed: #892. I would really like to see the SSH extension to work within code-server and would be happy to test it once there is any fix.
I currently have a need for Remote - SSH extension and unfortunately the official one doesn't work for me (which is unlikely to be solved upstream in the near future). So I am considering implementing it myself.
At least initially I would like to have it as simple as possible. Without any fancy terminal forwarding or something like that. Just make it so that the work with the filesystem and all the language servers are running on the vm and UI is running in the vscode. Similar two what we now have with code-server in the browser, but without browser version problems (such as cmd+w for example).
Would you have some pointers as to where to start investigating from inside vscode source?
At the moment I don't have a good idea of the full scope of what'll be required to make this work but it'll probably have to do with using and/or implementing the remote authority stuff.
There's a workspace.registerRemoteAuthorityResolver in the proposed API which might be a good starting point.
Is there any more direct way to add arguments to the vscode to execute ?
I'm not sure if the enable-proposed-api switch simply does nothing or there is something else to be enabled.
Activity
lukasmasuch commentedon Jan 29, 2020
In case this issue is about fixing the remote extensions to work with code-server, this related issue can be closed: #892. I would really like to see the SSH extension to work within code-server and would be happy to test it once there is any fix.
sr229 commentedon Jan 29, 2020
@nhyoor if this interests you, there's a remote subfolder in the main vscode folder, wanna
abusereuse that?frank-dspeed commentedon Feb 1, 2020
The remote extension does some checks as far as i know i decompiled it some times.
There is a validation shema i think we should first automate the decompile process and check that.
nhooyr commentedon Feb 2, 2020
We cannot and will not decompile the extension, that is not valid per the license terms.
Just-Insane commentedon Feb 23, 2020
Is there any further plan to implement these extensions?
kirscheGIT commentedon May 29, 2020
Would also like to know, if you have still have plans to implement this. Thanks!
code-asher commentedon May 29, 2020
Nothing concrete at the moment.
gyzerok commentedon Jun 5, 2020
I currently have a need for Remote - SSH extension and unfortunately the official one doesn't work for me (which is unlikely to be solved upstream in the near future). So I am considering implementing it myself.
At least initially I would like to have it as simple as possible. Without any fancy terminal forwarding or something like that. Just make it so that the work with the filesystem and all the language servers are running on the vm and UI is running in the vscode. Similar two what we now have with code-server in the browser, but without browser version problems (such as cmd+w for example).
Would you have some pointers as to where to start investigating from inside vscode source?
code-asher commentedon Jun 8, 2020
At the moment I don't have a good idea of the full scope of what'll be required to make this work but it'll probably have to do with using and/or implementing the remote authority stuff.
There's a
workspace.registerRemoteAuthorityResolver
in the proposed API which might be a good starting point.JayDoubleu commentedon Aug 17, 2020
building from vscode-1.48.0 branch + adding 9fb33dc , as well as adding
ms-vscode-remote.remote-containers
toextensionAllowedProposedApi
.This gets the remote extensions installed however it is still complaining with the error:
Tried executing via below.
Is there any more direct way to add arguments to the vscode to execute ?
I'm not sure if the enable-proposed-api switch simply does nothing or there is something else to be enabled.
69 remaining items