The one (big) caveat is that some Emacs commands that start subprocesses will incorrectly try to start the process in your local environment (in this case, on t

The one (big) caveat is that some Emacs commands that start subprocesses will incorrectly try to start the process in your local environment (in this case, on the Windows side), rather than the remote environment (within the WSL VM). This mainly occurs when elisp functions are implemented using call-process or make-process when they should use process-file[1] or start-file-process[2]. This isn't an issue for most code within Emacs itself, but it pops up occasionally when using packages from ELPA or MELPA. [1] https://www.gnu.org/software/emacs/manual/html_mono/elisp.html#Synchronous-Processes https://www.gnu.org/software/emacs/manual/html_mono/elisp.ht... [2] https://www.gnu.org/software/emacs/manual/html_mono/elisp.html#Asynchronous-Processes https://www.gnu.org/software/emacs/manual/html_mono/elisp.ht...