3 ms·
My experience with Cygwin back in college (~2008) was that it was obtuse and hard to understand. Granted, I didn't have the knowledge of *nix CLI I have now. B
by otachack 5y ago
My experience with Cygwin back in college (~2008) was that it was obtuse and hard to understand. Granted, I didn't have the knowledge of *nix CLI I have now.
But looking back and comparing it to Git Bash experience of today, with a simple installer to run, Git Bash wins in convenience. It does suck in other areas though such as trying to start a Python interpreter session (I fallback to PowerShell for that)
Cygwin has probably grown a lot better since but I don't see a reason to try it, personally.
- ChrisSD 5y agoWhat's the Python issue?
- lozenge 5y agoThere's no package manager so there's no way to install things and there's no Python included. You could run your Windows Python but the paths will be wrong (C:\ instead of /c/), etc.
- pletnes 5y agoGit bash will translate /c/ to C:\ so that’s only sometimes true. But it won’t translate //c/ or if you set a certain env var… etc. Having to recall all these rules is one reason I dislike working in git bash on windows.
- jliu70 5y agoThe workaround to running the python interpreter from git bash is to preface python with the command winpty like so `winpty python` Reference: http://willi.am/blog/2016/08/08/docker-for-windows-interactive-sessions-in-mintty-git-bash/ http://willi.am/blog/2016/08/08/docker-for-windows-interacti...
- otachack 5y agoI'll try it out! Thank you.