[bemusedthrow75]

I guess Tramp mode must be the inspiration, to some extent.

But the VSC approach allows me to customise the tool environment within the remote extension, including going as far as using different SCSS processors and language servers, but is managed through essentially exactly the same interface as the local.

(It's also inherently multi-user; changes are reflected in each machine connected to the remote, which makes it really easy to move from a work to a home machine, or a desktop to a coffee-shop laptop.)

This is what I meant by uniquely-implemented. I often find that the most visceral critics of VSC or adherents of "natively implemented" code editors haven't the slightest awareness of this feature.

Still -- thank you for your comment, it gives me one more thing to investigate for those times when tools fail me.

[flamwenco]

Yeah, I certainly didn't mean it as a slight against VSC. (I am very much an electron hater but VSC is an exception because they obviously put in the effort to make it work as well as it does.)

Much as I love Emacs I do mostly use VSC these days, and I do tend to forget the extent of what remote editing capabilities it provides since I haven't had much reason to use them in a while.

[bemusedthrow75]

Yes -- sorry, my comment about critics may have come across as aimed at you, but it wasn't!

I was thinking more of all the other times this has come up in the past and I have to say, "you understand it's not just a text editor with network access?"

It has pretty much unique capabilities, and as another commenter has said, it's even remarkably agnostic as to the _kind_ of remote container. For example you can run the editor on Windows with the remote as WSL, and it really blurs the boundaries between them in a way that cannot possibly be a coincidence for Microsoft.