-
Notifications
You must be signed in to change notification settings - Fork 373
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
Panics on Bash on Windows #174
Comments
Quick update - commenting out the |
Looks like this might be addressed in Insider builds of Windows: microsoft/WSL#601 |
Also termbox-go works natively on windows (via windows console backend). Sure you might prefer it to run via bash for whatever reason. But I never tested it this way. |
+1, spent a couple hours trying to diagnose and solve this last night, running inside Linux Subsystem for Windows. I also don't know anything about syscalls so my plan is to try rewriting the project with termui :( |
I don't think mine is different enough to create a new issue. Just going to drop this here: $ go get -u github.com/nsf/termbox-go
$ go run ~/go/src/github.com/nsf/termbox-go/_demos/keyboard.go
panic: invalid argument
goroutine 1 [running]:
panic(0x5469e0, 0xc82000a738)
/usr/lib/go-1.6/src/runtime/panic.go:481 +0x3e6
main.main()
/home/j/go/src/github.com/nsf/termbox-go/_demos/keyboard.go:663 +0x88
exit status 2 Windows BASH |
Did you eventually discover that termui is built on termbox-go? Did you find a different approach? |
I don't know if anyone is still interested in this, but just in case: Let me know if your issue persists and we'll look into it! |
Running the keyboard demo fails with a panic. It's on line 47 of
api.go
and the error is ultimately returned from
fcntl
intermbox.go
:Looks like someone else has had a similar issue: https://stackoverflow.com/questions/45911874/termbox-library-can-not-be-initialized-at-termbox-go
I won't pretend to know anything about syscalls but let me know if I can provide any more information.
The text was updated successfully, but these errors were encountered: