News for hackers. Stuff that matters.
Re:Getting Started with Git Bash by otachack on Saturday February 05, 2022 @10:56AM (#30222276)
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.

Re:Getting Started with Git Bash by jliu70 on Saturday February 05, 2022 @01:39PM (#30224226)
The 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-interacti...

Re:Getting Started with Git Bash by otachack on Monday February 14, 2022 @11:26AM (#30333922)
I'll try it out! Thank you.
Re:Getting Started with Git Bash by ChrisSD on Saturday February 05, 2022 @11:02AM (#30222354)
What's the Python issue?
Re:Getting Started with Git Bash by lozenge on Saturday February 05, 2022 @11:46AM (#30222911)
There'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.

Re:Getting Started with Git Bash by pletnes on Saturday February 05, 2022 @12:32PM (#30223450)
Git 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.