-
Notifications
You must be signed in to change notification settings - Fork 227
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
Keystrokes don't work on OpenBSD #160
Comments
That's indeed strange. At the moment I have no idea what might cause it. Can I ask you how you installed slack-term, via binary or go? |
Compiled it from source using go. (Using the go compiler from OpenBSD ports)
On Mon, Sep 17, 2018, 5:20 PM JP Bruins Slot ***@***.***> wrote:
That's indeed strange. At the moment I have no idea what might cause it.
Can I ask you how you installed slack-term, via binary or go?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#160 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AO5m4cThM-YnGl2kvbhU6kGtJUGNV_nzks5ub00ngaJpZM4WqyJY>
.
--
--
Greg Baker
+61 408 245 856
|
FWIW I am seeing the same problem on openbsd 6.6 with slack-term compiled from source. Slack loads properly but I am not able to do anything (including quiting). Running with the Here are some additional details in case it's helpful.
|
Hi, reporting same issue as @levlaz. OpenBSD 6.6, slack-term installed via |
This is also reproducible on FreeBSD. I created a branch slack4bsd to test if this issue could be resolved with merging some fixes. Like FreeBSD keybindings fix and unsupported block type Please check if this is useful. |
I at least merged the keybindings fix from nsf/termbox-go. Check if this resolves the problem |
This fixed the problem. Thanks a lot! |
I can supply a login to an OpenBSD system that demonstrates the problem.
When I start slack-term, no keystrokes do anything, even using a .slack-term file that works fine on a Linux box. When I kill the slack-term process, whatever I type ends up in the surrounding shell, as if they've never even been read in by the slack-term process.
The text was updated successfully, but these errors were encountered: