macos version difficult to use about boltbrowser

[br0xen]

I'll have to try to track down a mac to test this on. It may be your terminal config, though. I've seen issues similar to this before where terminal configuration fixes it (not saying that's the issue for sure, but it's possible.)

[utdrmac]

What settings should I use? What terminal type/etc?

[br0xen]

I was able to test it on a mac in the default terminal app and it worked fine. Have you tried it with any other settings? I apologize, I just don't have easy access to that setup so I don't really know the direction to point you in. I'm asking around to some friends that are more familiar with Mac that may be able to help.

[utdrmac]

I tried it using default terminal app and it worked fine. I use iTerm2 (more advanced features, etc over terminal) I narrowed it down to this: export TERM=xterm-256color This is the default terminal type in Terminal.app but I use vt100 (older but way more compatible). I set this in Terminal.app and got same behavior. In iTerm2, set to xterm-256color and it worked. Maybe next minor version could test for this?

[br0xen]

I apologize, but I'm not sure what else to do about this issue. As I mentioned, I don't have easy access to a mac, but everyone that I have had do testing on a mac hasn't been able to reproduce it... I'm going to close the issue, if others start showing up with the same problem we can revisit it.

[utdrmac]

No worries. It's been working fine for me when I use export TERM=xterm-256color. Since that is not my default TERM, it would have been nice to see a requirement or a warning printed that says "you need to use xterm-256color" or just have the app set that for me on startup if detected otherwise.

[br0xen]

Oh, interesting... Good to know, maybe I'll put something in the readme about that. It looks like people experience other issues with the termbox library depending on their Terminal/TERM combination. :P Thanks!

…

On Wed, Oct 24, 2018 at 8:32 AM Matthew ***@***.***> wrote: No worries. It's been working fine for me when I use export TERM=xterm-256color. Since that is not my default TERM, it would have been nice to see a requirement or a warning printed that says "you need to use xterm-256color" or just have the app set that for me on startup if detected otherwise. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#25 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABNtwJBkVukhwy0w4rAvV0QAYly8n-mHks5uoGvWgaJpZM4Tkh4t> .