My newest yocto image mounts a 640K RO tmpfs on top of $HOME/.vscode-server to prevent people using VSCode from shitting all over the relatively small emmc.
My newest yocto image mounts a 640K RO tmpfs on top of $HOME/.vscode-server to prevent people using VSCode from shitting all over the relatively small emmc.
640k … there is something poetic about that number.
I figure that's how much RAM I can expend for Microsoft products.
Can you explain how this works? Doesn’t this also stop you from connecting to it over ssh via vs code?
Yes that's the point. If vscode didn't insist on installing potentially gigabytes of blobs then this wouldn't be necessary.
(I'm a vimmer anyway... And emacs is too bloated to fit too, conveniently.)
> And emacs is too bloated to fit too, conveniently.
If you connect via ssh, you could use Tramp. It does not install emacs on the target, but instead use a somewhat permanent connection as a tunnel for most emacs commands (transparently). Works too with docker, podman, distrobox, etc,...
yep, it's a shame vscode doesn't do something similar and instead copies a huge runtime (evidently, multiple times?!?) onto unsuspecting hosts.
Sounds like a feature.