4 ms·
Also you can't interact with the WSL directory outside in a graphical text editor or File Explorer. There's going to be someone who responds to this saying it w
by PascLeRasc 8y ago
Also you can't interact with the WSL directory outside in a graphical text editor or File Explorer. There's going to be someone who responds to this saying it works for him, and I'm very happy for you. Every time I create a folder in the WSL directory in File Explorer it's permanently un-cd-able in WSL, and vice versa. Editing text files outside corrupts them. Yes, I've tried reinstalling.
WSL is just a shitty implemention on a shitty OS. Linux and OS X work perfectly and they have package managers and I can control updates.
- bproven 8y agoYeah - I generally touch files or create dirs in WSL first to get around it. Otherwise it is a cluster. If i could just use Linux @ work I'd be much happier.
- CodeCube 8y agoThe trick here is to not use any windows program to modify anything on the WSL file system (because of the unix permission system). But it works vice-versa ... so you can use any unix program to modify a file on the windows file system. So my hack there is to simply make a symlink in my unix dir (`~/dev`, usually) that points to a folder on the windows file system ... that way I just do all my work in ~/dev and it's all good.
- setquk 8y agoWhat’s the point then? Cygwin works better than this.
- gpvos 8y agoYes, you should have heeded the warnings against that. The article also mentions this in passing. You can get at Windows files from WSL, but don't do it the other way round.
- Zekio 8y agoyou can get package managers on Windows as well, such as chocolatey or https://scoop.sh/ https://scoop.sh/