Add support for WSLg #39
Conversation
|
The solution proposed in #40 sounds more future-proof than this one. The activation script would still be needed for the start menu application launchers to work though |
|
This PR now includes the changes from #45 instead of hard-coding the environment variables. New changes included here are the customizable mount path for windows drives as well as copying application launchers to |
| @@ -13,6 +14,9 @@ in | |||
| # WSL is closer to a container than anything else | |||
| boot.isContainer = true; | |||
|
|
|||
| # Include Windows %PATH% in Linux $PATH. | |||
| environment.extraInit = ''PATH="$PATH:$WSLPATH"''; | |||
There was a problem hiding this comment.
That has one downside: It slows down tab completion down tremendously because looking up the windows directories is very very very slow.
See akinomyoga/ble.sh#96 (comment) for some details.
There was a problem hiding this comment.
From what I understand, this is a problem for all WSL distros. Appending the path can be toggled off with wsl.wslConf.interop.appendWindowsPath = false;. #64 has an option to toggle off the extraInit code
This PR adds support for WSLg.
GUI Applications can be launched from a shell as well as from the start menu
I added an activation script, that copies the application launchers to
/usr/share/applicationsso that the installed applications will appear in the windows start menusyschdemd.shwas changed to start/bin/shas a login shell because the environment variables aren't present otherwise