-
Notifications
You must be signed in to change notification settings - Fork 96
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
Ruby 2 at Mac OS X: couldn't initialize curses color pair 4 #191
Comments
Weird, do you have a custom colormap.rb in: ~/.sup? Do you get this error when you try to start Sup the first time or do you do something else? Could you please turn on debugging: export SUP_LOG_LEVEL=debug and try again so that we'll get some more output. Thanks, gaute |
As for special setups, I'm running ZSH in iterm2 (custom colors in iterm), wrapped in tmux. Obviously on a mac. |
|
When firing up sup. Bare install as via the gmail + macosx tutorial. Also, I tried setting the color profile in my term back to default, using bare bash, no tmux and setting LANG is btw set to utf-8 across my terminal. Could that have negatively affected the ncurses compile some how, I don't know, like mapping the wrong color codes to the wrong colors? I'm just yak shaving here.
|
Excerpts from Timon Vonk's message of 2013-11-27 10:29:14 +0100:
yak should be shaved, utf-8 is the way to go. shouldn't be a problem: as could you try with just plain mac os x Terminal.app and no other special what version of Mac OS X do you run? did you do the 'brew link ncurses' I can't test much more right now.
|
Disabled as much as I could, nothing :(
Mavericks, all linked well. Also tried a relink and a |
Ok, I run pretty much the same setup as you. Except I use Ruby 1.9.3 through RVM, maybe worth a shot? I also have all Xcode CLI tools, but you probably needed to install that yourself? The correct, wide char supporting, ncurses must be installed and linked (--force) before the gem is installed. Doing a pristine install should have taken care of that anyway (you could try to do brew doctor before installing the gem as well). |
I run a setup very similar (Mavericks, iTerm2, tmux) and had the same issue until I switched to using Ruby 1.9.3. Steve
|
No. Way. That did it. |
Excerpts from Timon Vonk's message of 2013-11-27 14:58:29 +0100:
Cool. So it is a Ruby 2.0.0 Mac OS X specific issue 😀
|
There's such a thing as oss continuous integration servers. |
We do have some testing using Travis (including Ruby 2.0.0), but not |
Cool! Thanks for the help @gauteh and @k2enemy ! Closing this. A remark in the readme and/or osx install instructions would be awesome! |
Excerpts from Timon Vonk's message of 2013-11-27 15:21:53 +0100:
sure! help yourself to the wiki ;) we could probably keep this open. it should be fixed at some point. |
Sure, thanks! But isn't it more likely a bug in ncsursesw-sup? |
Excerpts from Timon Vonk's message of 2013-11-27 15:44:21 +0100:
that could be.. but it breaks Sup so I think it should be kept open anyway. |
FYI running on 2.1.2 and all is good. |
Aight! Thanks for letting me know! |
Hey guys,
Fresh install of supmua, and I get this error.
Ncurses version is latest 5.9 from brew.
The text was updated successfully, but these errors were encountered: