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. |