3 ms·
> Do you mean "remote development", ssh/scp-ing with the container? I think they are referring to the integration of VSCode with Docker. I.E. build, deploy and
by heywoodlh 4y ago
> Do you mean "remote development", ssh/scp-ing with the container?
I think they are referring to the integration of VSCode with Docker. I.E. build, deploy and run your project in a clean container environment quickly using a workflow that is intuitive to VSCode users.
That being said, I know for me it would be fairly trivial to workout this same type of integration for myself with Vim. Although I am not an Emacs user I am positive it wouldn't be difficult to do something similar. I don't really see this as a feature I would ever care to implement or find important for myself.
EDIT: to be clear, I am a Vim user and do not find VSCode intuitive at all -- but I have seen how it seems to really work well for a lot of people
- morelisp 4y agoEmacs uses the same mechanism to work inside a container as it does to work over SSH, which is also the same mechanism it uses to work as a different user on the same machine, and pretty much anything you can get something FS/shell-like on. Multiple container runtimes, k8s clusters, git repositories, etc. It's essentially a full VFS layer, although (like most VFS layers) it's clunky if you try to compose certain things. E.g. remote debugging isn't going to work on your HDFS cluster... https://www.gnu.org/software/emacs/manual/html_node/tramp/index.html https://www.gnu.org/software/emacs/manual/html_node/tramp/in... https://www.gnu.org/software/emacs/manual/html_node/tramp/Customizing-Methods.html https://www.gnu.org/software/emacs/manual/html_node/tramp/Cu...
- ParetoOptimal 4y agoI posted how to do it without ssh using docker-tramp elsewhere in thread FYI.