-
Notifications
You must be signed in to change notification settings - Fork 30.5k
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
Edit over SSH #44378
Comments
Kind of a dupe of #29194 but once that (monster) item is done extension will be able to implement this. There is already a experimental implementation for ftp doing this (see https://github.com/jrieken/ftp-sample). So, ultimately closing as 'extension-candidate' but the API hasn't been finalised yet. |
We try to keep VS Code lean and we think the functionality you're asking for is great for a VS Code extension. Maybe you can already find one that suits you in the VS Code Marketplace. Just in case, in a few simple steps you can get started writing your own extension. See also our issue reporting guidelines. Happy Coding! |
Yup, that's what it will be |
We just announced remote development with VS Code, check out the blog post for details |
Issue Type
Feature Request
Description
I would like an action, "Open Remote File (SFTP)", that would open a file on a remote system, using SFTP (SSH FTP).
This would
This would not
Why this is not a duplicate?
Technically, this is a duplicate of #23076. However, that issue was incorrectly closed as a duplicate of allow reading from stdin (#7320/#6161). This was incorrect as "remote editing by SSH" is very different from "allow reading from stdin".
This is distinct from #27423 as that issue is "open remote folder via SSH", not file. From a UI perspective, opening a file is much simpler, as the only UI needed is an editor pane and a few commands. A remote folder requires the contents of that folder to be displayed somewhere, such as the explorer pane.
VS Code Info
VS Code version: Code 1.20.1 (f88bbf9, 2018-02-13T15:34:36.336Z)
OS version: Windows_NT x64 10.0.16299
The text was updated successfully, but these errors were encountered: