Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: You killed windows again #1326

Open
xpusostomos opened this issue Nov 18, 2024 · 0 comments
Open

Bug: You killed windows again #1326

xpusostomos opened this issue Nov 18, 2024 · 0 comments
Labels

Comments

@xpusostomos
Copy link

I've long pointed out here that the cygwin version of bash is a perfectly fine version of bash, and as long as you don't pollute any variables with unixy paths (if you don't want that), there is absolutely no reason it shouldn't work.

Well low and behold, a few months back, cygwin started working again! And there was rejoicing in the land! And indeed it still works!!

Well kinda, it works on my old machine. But when I go to install it on a new machine, it doesn't work. Seemingly ... because it doesn't install ~/.sdkman/libexec executables. My old machine has those executables, and it works fine with cygwin.

So the documentation alleges that it works with MSYS2/Mingw bash. So I installed that, then installed sdkman again, and same thing... it doesn't work, and no libexec subfolder.

Now if I do set -x on my old machine, and do sdk help, it detects libexec, and calls the help executable to output help. But on the new installation it doesn't detect it, and it echos via bash all the help text.

It seems to me, that someone needs to do some very trivial work to detect cygwin, and/or MSYS2, and simply install libexec, and then the people in the land can go back to rejoicing again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant