1. 1
  1.  

  2. 3

    I’ve been using cygwin for many years, and I found if I simply install everything from cygwin, I have zero problems. The problems come when cygwin doesn’t have software in it’s catalog, like node, and go. Even then if I export them to my path in .bashrc I seldom have problems. When I do have problems it’s with someones custom script or utility that tries to set absolute paths based on the platform. Generally some internal script a windows user created.

    You can do a lot of stuff with cygwin. I’ve developed apache modules with it for example. I haven’t even tried WSL, I haven’t felt the need.

    1. 1

      I am curious what problems the author had editing from WSL in the windows file system. /mnt/c contains the whole c drive and in my case I have symlinks set up in wsl to redirect me to specific parts of the windows directory structure from there, like for example my one drive synced folders. And as for editing windows files with a WSL vim, well a simple :set ff=dos will do the trick. Also WSL supports more than just Ubuntu now for the linux instance.

      1. 1

        It’s the other way around. Editing a Linux file directly from Windows can mess things up badly.