> I want to work on files in my WSL home folder. Lots of language based package managers like npm and composer "live" inside a folder in your home directory. It's very important that VSCode running as a windows application be able to read/write to these files.
No. You don't want this. Linux and Windows are different platforms; if your Windows application could use your packages installed through Linux (and vice versa) then none of the native modules would work without a reinstall.
The side effects suck and they can make it better IMO but not sharing dependencies isn't an issue at all IMO.
> As it is right now I can't even edit my ~/.ssh/config from VSCode without jumping through hoops.
Yeah that sucks though for some things like git bash, etc, they use the proper windows home directory. So I end up just keeping those there and straight up copying or aliasing them to the WSL home folder.
No. You don't want this. Linux and Windows are different platforms; if your Windows application could use your packages installed through Linux (and vice versa) then none of the native modules would work without a reinstall.
The side effects suck and they can make it better IMO but not sharing dependencies isn't an issue at all IMO.
> As it is right now I can't even edit my ~/.ssh/config from VSCode without jumping through hoops.
Yeah that sucks though for some things like git bash, etc, they use the proper windows home directory. So I end up just keeping those there and straight up copying or aliasing them to the WSL home folder.
It's not a great experience but it works.