If there's ever been a great opportunity to open source something in the Windows client, it's WSL. A number of popular User Voice feature requests were closed recently as not in scope, which is reasonable on the part of the WSL team but shows that the demand for Linux-on-Windows is much greater than the team's current objectives. If the project was open source and the team accepted patches who knows where this thing could go. People want to run X, they want device emulation, they want to run all kinds of apps that aren't necessarily dev tools.
Invoke Win32 applications with Bash on Windows
51–52 of 52 posts
Re: Invoke Win32 applications with Bash on Windows
#52Earlier quoted context omitted.
If you had to you can touch things in the WSL VolFS by browsing the appropriate %AppData% subfolder. I'm presuming Microsoft isn't encouraging that right now with this Interop tooling for several reasons. At a guess one of them might be that apparently the Unix things like permissions and Unix-style metadata are stored in NTFS alternate streams (~"resource forks") that they may be worried some Windows programs might…
It actually doesn't work right, and MS just closed the issue. I'd be fine with cifs automounts in the linux subsystem for windows file directories... I mean it may take a little work, but in the end, I want to edit files with a windows gui editor, and run them via the LSW applications. Until I can do that, it's an also ran on the desktop... and until it can be used for docker with linux containers on the server, it d…
Why can't you keep the shared files that you want to GUI edit somewhere under /mnt/?/* in a normal NTFS folder? That works fine already today.
I'm using Bash on Ubuntu on Windows for Jekyll (because installing and keeping up to date Ruby on Windows is a terrible experience and this is a much nicer alternative). My files are in D:\Repos\..., I'll have VSCode open and Jekyll running in Bash in the equivalent /mnt/d/Repos/...