fokicollector.blogg.se

Smartgit vs gitkraken
Smartgit vs gitkraken











smartgit vs gitkraken

However I don't think that's a viable solution since the whole point of WSL (for me) is to be able to use Windows-based editors such as full VS with a Linux dev environment.

  • I'm aware the WSL team suggests that with WSL2 it's good to store your application sources inside the Linux filesystem instead of the Windows one.
  • Unable to save file when inotify is in use (using Node) #1956 is about a different scenario, File contents differs on mounted Windows drive between Windows and WSL #4064 isn't specifically about change notifications, File watchers like create-react-app, gulp or sass doesn't work #4224 is closed, WSL2 Increase the maximum amount of inotify user watches #4293 doesn't fix it. However I was unable to find any open GitHub issue that specifically tracks this.
  • I strongly expect this is already a known issue as hinted here.
  • This unfortunately renders many modern dev workflows unviable. This means that all "live rebuild"-type tools don't work (examples: webpack -watch, jekyll -interactive, and v) when running under WSL2.

    smartgit vs gitkraken

    Great job! One missing feature however is breaking a core part of the developer flow.įor sources stored on the Windows filesystem, any changes made by Windows applications such as Visual Studio do not trigger any file change notifications as far as Linux apps are concerned. WSL2 is really close to being a perfect runtime environment for server apps being developed in Windows.













    Smartgit vs gitkraken