5 ms·
However, this is thing: http://www.ghacks.net/2016/11/21/microsoft-dont-edit-linux-files-on-windows/ http://www.ghacks.net/2016/11/21/microsoft-dont-edit-linux
by notalaser 10y ago
However, this is thing: http://www.ghacks.net/2016/11/21/microsoft-dont-edit-linux-files-on-windows/ http://www.ghacks.net/2016/11/21/microsoft-dont-edit-linux-f... . Half the reason why I'd consider making the switch is being able to keep on using my CLI tools while still having access to sane UI tools.
- danieldk 10y agoAs far as I understand, it works fine if you store data outside %localappdata%\lxss. So, just put it on your regular C-drive and make a symlink from your home directory for easy accessibility. But I agree that it would be great if they could solve this in the future.
- leonatan 10y agoYou can. Just edit the files on NTFS, and access them from the mount folder from the CLI. The article is about editing the subsystem files themselves.
- notalaser 10y agoTrue, it's just somewhat unpleasant to have to remember where the file you're editing is and wonder if it's safe. The good news is that a lot of these things are getting fixed. E.g. it used to be that path expansion for executable files lookup didn't work too well (as in, you could launch native Windows executables only via direct path, because the subsystem would otherwise check for an ELF header, so you couldn't launch foo.exe in your $PATH just by name), but I understand that this is getting changed in upcoming releases. I'm keeping an eye on this thing, it is promising. I'm so looking forward to putting all the Red Hat-branded breakage behind me and not have to wrestle with my computer all day.