And then, how do I use bindfs with WSL ? Where are the WSL files and the docker volumes inside it ?
The app and having a window open of that app are decoupled, simple as that. Open up, say, Safari, press Cmd+W to close the window, and Safari will still be open. Press Cmd+N and you'll open a new window. Press Cmd+Q to quit it, regardless of how many windows (including zero) are open.
In WSL1 files are stored in a protected folder of %LocalAppData%. It's protected because using Windows and regular NTFS-expecting tools has a bad tendency to mess up Linux ACL metadatda. More recent versions of WSL1 added a Plan9-based file server that shows up as a pseudo-device in Windows under a UNC path \\wsl$
In WSL2 the files are stored in a VHD-like file (VM hard drive) and the Plan9-based file server is always available in every version of WSL2 (under \\wsl$ still) and additionally used in both directions (/mnt/c/ is no longer a direct NTFS mount on the Linux side, but now uses the file server, because WSL2 is more VM-like in every facet).
/usr/bin/bindfs --force-user=johnchristopher --force-group=johnchristopher --create-for-user=www-data --create-for-group=www-data /home/johnchristopher/.docker-data/volumes/web/_data /home/johnchristopher/Dev/Web
But it could be done in WSL2 (keeping permissions intact in the volume while being able to edit them outside) ?
This is about the only gripe I've had with linux desktop in recent years. For everything else, its been at par or better than windows/osx for me. I do mostly programming, music synthesis/recording and photogrammetry/image processing on a Dell XPS-15, and its been great.
- use alsamixer to find out which mic is which and if they are muted (it's a CLI app)
- install blueman to have it easier to switch the headset to hsp/hfp (a2dp sink is one way and it means it's not designed to send sound from the headphones, I made that mistake)
- since I have a Dell I had to fight that pesky mute led status in alsa (haven't figured out yet what it means, I ended up disabling the internal mic in the bios to be sure it was the headphone doing the recording) ; there are bug reports about the keyboard key not doing what it's supposed to do ; the internal mic only works when I set it to On in the alsamixer menu ; you can check if the laptop led is on or off (like the webcam) ;
- use pavucontrol to try to figure out what device is doing what (it's like the sound control center but it displays more information)
- make sure to switch off every device that is not your headset/headphone (hdmi, internal, anything) ; it's funny how you can configure an audio stream (say your laptop's internal speakers) to be the recording stream: it'll just record itself
I also installed audacity and recorded myself muttering "blah blah" way too many times in order to try to identify the microphones detected by the system. I still don't understand why I have so many redundant output devices with the same name and an incremental version (:1, :2, :3) but hey.. it works (I just want to be able to video call two colleagues tomorrow, I really don't know how to control for quality if you have studio quality sound recording needs :/).