-
Notifications
You must be signed in to change notification settings - Fork 317
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
OS X 10.10 no longer includes Ruby 1.8 #84
Comments
Incidentally, the failure mode here is quite horrible. If I try and use Command-T with Ruby 2.0, I get a forkbomb (ruby calling sh calling ruby, ad infinitum) |
Command-T doesn't require 1.8 (or any specific version of Ruby). It will use whatever Ruby you compile it with (and that's generally based on what you have in your I gather you're not on a clean install of 10.10, so you should just rebuild Command-T against the system Ruby:
|
Hrm, the documentation referenced Ruby 1.8 multiple times and I thought that was the required version. But it appears that was a misinterpretation of the docs. I already tried recompiling command-t itself. I'll try again though. |
Yeah, the docs say this:
I'll update the docs with info about Yosemite as well. |
You're right, this time it worked without forkbombing. I'm not sure what went wrong last time, but forkbombing is the behavior I was seeing with Homebrew trying to run its Ruby 1.8-compatible code on Ruby 2.0, so that's what I thought was going on here. I'll leave this open to cover updating the docs I guess. |
Deal. 👍 |
Command-T requires Ruby 1.8, but OS X 10.10 no longer includes it, and the vim that ships on the system includes ruby support using ruby 2.0.
/usr/bin/vim
provides Ruby version2.0.0-p451
.The text was updated successfully, but these errors were encountered: