kiskae / config Goto Github PK

working theory:

.vscode-server/setup-server-env is called by <windows_vscode>\data\extensions\ms-vscode-remote.remote-wsl-0.81.4\scripts\wslServer.sh`.

It in turn first sets up the env, then calls a sibling script wslDownload.sh to download the server if needed.

What if we called wslDownload during server setup and then do binary replacement as required. This could ensure atomic access to the server for modification and means no more checking is required to get it to work.

Current solution: https://github.com/sonowz/vscode-remote-wsl-nixos/tree/master
Useful data: microsoft/vscode-remote-release#1744

Perhaps replace node with our own full env setup, since WSL invokes it by directly launching the node binary. Without going through any standard shells.

requires wsl -d NixOS uname to succeed. Uses WSL-defined path so can't find /run/current-system/sw/bin.

socket-activation seems to break