Gum for Git Bash / Cygwin
Is your feature request related to a problem? Please describe. I am not able to use gum in my work because we work with GIt Bash for Windows. The Git Bash seems to use Cygwin to simulate unix command line. I usually can run all sorts of bash scripts without any errors, but gum.exe is not working because it was not compiled for Cygwin.
Describe the solution you'd like I would love if it was possible to have gum compiled for Git Bash/Cygwin.
Describe alternatives you've considered I could not think of any alternatives for the moment.
Additional context
This is the error I get when I execute gum from bash:
failed to get console mode for stdout: The handle is invalid.
failed to get console mode for stderr: The handle is invalid.
This is the Git Bash I use: https://git-scm.com/download/win
I would love if it was possible to have gum compiled for Git Bash/Cygwin.
It seems to be either a configuration issue or a MinTTY specific issue. When I run it on machines where I have Windows Terminal or Fluent Terminal installed I can run gum.exe without problems using %ProgramFiles%\Git\bin\bash.exe. I can even run gum in PowerShell 7 and the old preinstalled PowerShell. So there is either a sub optimal configuration in MinTTY which could be solved in upstream MinTTY or in your dotfile collection (not per se your minttyrc, which you apparently have); or it is broken in MinTTY like a few other things, entering passwords which are are not hidden but echoed in plain text on the terminal for example (1, 2). Cygwin is not a solid foundation to build on, it comes with a list of issues. Yeah I'm also using and tinkering with Git-Bash and a few other tools on Windows, but that does not change the fact that Cygwin is de-facto abandonware and Microsoft opted to build WSL1 and WSL2 not just for fun of reinventing the wheel.
I am not able to use gum in my work because we work with GIt Bash for Windows.
They are ignorant idiots who jump to conclusions. See my remark above. I have seen other ignorant people build pipelines with Cygwin which took hours more to complete than necessary for quite simple tasks. But of course nobody can stop idiots from burning customers' money in the absence of sanity and willingness to read and understand what kind of components they consume and how. You need bash in your workplace to get work done? Great, stop using Cygwin! Tell your employer you need WSL, a Chromebook, a Mac, your preferred flavor of Linux or a corporate friendly and paid version of Linux (Red Hat, Suse, Ubuntu). ... or learn writing PowerShell when on Windows, it's not my favorite language either, but manageable. Sounds contradictory? Bash is so great? Read this: https://www.oilshell.org/blog/2021/01/why-a-new-shell.html
I usually can run all sorts of bash scripts without any errors, but gum.exe is not working because it was not compiled for Cygwin.
You have a misconception there. No, there should not be a Cygwin flavored build from my point of view. It's a static go binary for Windows which runs fine on Windows in every other Terminal and Shell I have tried. I have run other go binaries like chezmoi and k9s too on Windows, no special Cygwin flavor required. From my point of view it's an issue with MinTTY. It may be quickly fixable for one well versed programmer, but as long as Git-Bash does not ship with gum or other go binaries, I'd say yeah you can do some cool tricks in an environment which was just a stopgap, but you shouldn't.
think there's a similar issue reported, and been fixed by @muesli but still has 2 Open PRs upstream: https://github.com/charmbracelet/gum/issues/32
- https://github.com/containerd/console/pull/66
- https://github.com/containerd/console/pull/67
Thank you for letting me know. Your response was very kind
@miguelcjalmeida Those PRs were merged upstream can you double check that this is still an issue?
This still gives an error, when using the assignment:

I am using git bash