![]() ![]() I would strongly recommend using the setup Nick Janetakis outlines in his blog here: I am curious to see others' thoughts on this. It seems WSL is probably going to be stuck in a CLI, non-GUI existence indefinitely since it's not intended to turn into a MacOS or compete with Windows 10. So for now, it looks like a question of priorities: if I want a Linux work environment and Jetbrains I probably need to run a full Linux distribution in a VM or as a dual-boot (or better, instead of Windows ^_* ) and if I want Jetbrains but Windows I should give up (for now) on WSL. OpenSSL in WSL is still at 0.1.0.0 (beta, i think) as of this writing, and will be much better fairly soon when it moves to 1.0.0.0 release but I don't know the timeline.Īnyway, The main thing I want to mention for this discussion is - that page is straight from MSDN developers and it is very clear about not working on one's WSL file system using Windows-based tools. ![]() Now we are living and working after the 2017 Fall Creators Update of Windows 10, and some Jetbrains help articles are out of date, because WSL is out of beta, is almost a one-click install from "Turn Windows Features on or off", and no longer requires "developer mode". ![]() ![]() Hi Elena and others, I hope it's not too late to add to this discussion 8 months later. Hope this helps shed more light on the issue. The likelihood of it being fixed in WSL is, um, "low". It would be nice if some compatibility setting could be added (if a compatible way of reading & saving files was determined). The same issue happens if both are trying to manage (at least git) version control, likely for the same reasons only with that, it gets so corrupted you have to re-clone the repo. For example running a JS test continually that listens for changes: WS tries to update the file but can't meanwhile the WSL tool either sees the filename changed below it or just sees a new temp file created, and then "dies", with neither side recovering until the test is stopped, the file is resaved, and the test manually restarted (which can be a very lengthy process). If there is a WSL tool running that is "listening" to a file for changes and then WS changes it, both sides get confused and/or broken. One specific issue seems to be in the way the WSL tools open files vs how Webstorm (at least on Windows) does. ![]()
0 Comments
Leave a Reply. |