This will be handled natively from within WSL. With the new feature, you'll be able to safely access both Windows and Linux filesystem files from Windows, as long as you go through the 9P server. The 9P server will be able to handle Linux filesystem metadata, and Windows will be able to treat it as a network drive so it can access it safely. Once it's ready, a 9P server will run in the background whenever a Linux distro is running. Microsoft has recently added comprehensive support for this, and it should be generally available in the April 2019 (19H1) update. Is there any way to get the best of both worlds here - that is, to be able to edit using a native Windows application, but still have the Linux toolchain work as it normally would on a local drive? However, the Linux-based toolchain is fragile as it's not designed to be used on a "network drive", and can cause problems with file watching or databases. Now any Windows-based editor can be used for development. Store the project under the Windows filesystem ( /mnt/c/Users/foo). However, editing is limited to either terminal-based Vim/Emacs or whatever can be run under a janky X server, which is less smooth than native editors running on Windows. Store the project under lxss ( /home/foo). Therefore, there seem to be only two suboptimal choices when it comes to using WSL for development: Directly modifying these files is known to cause all sorts of issues. The problem is that Windows apps cannot modify files inside the virtual lxss filesystem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |