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
Console task fails if ruby version has no readline support #1640
Comments
Why does |
My words exactly. All afternoon long. On 31 March 2014 20:42:38 CEST, Florian Gilcher notifications@github.com wrote:
|
The first one is pry, not padrino: https://github.com/pry/pry/blob/0-9-11-stable/lib/pry.rb#L219 |
I think this message |
@ujifgc The issue is that we fail if completion is unavailable, as it is just a convenience feature for IRB and not a necessity. A warning is more appropriate. Context: Ruby 2.0.0 and 2.1.0 seem to have issues building with recent readlines. |
Fixed! ~$ rvm install ruby --without-readline
~$ irb
Readline was unable to be required, if you need completion or history install readline then reinstall the ruby.
You may follow 'rvm notes' for dependencies and/or read the docs page https://rvm.io/packages/readline/ . Be sure you 'rvm remove X ; rvm install X' to re-compile your ruby with readline support after obtaining the readline libraries.
2.1.1 :001 > exit
~/app$ padrino console
=> Loading development console (Padrino v.0.12.0)
=> Loading Application Admin
Readline was unable to be required, if you need completion or history install readline then reinstall the ruby.
You may follow 'rvm notes' for dependencies and/or read the docs page https://rvm.io/packages/readline/ . Be sure you 'rvm remove X ; rvm install X' to re-compile your ruby with readline support after obtaining the readline libraries.
2.1.1 :001 > ^[[A |
I've (inadvertently) installed ruby without readline support and tried to run padrino. The
start
task fails gracefully, while theconsole
task spits out the whole stack:Looks like the readline check for 'console' is missing.
I'm using padrino-core 0.11.4
The text was updated successfully, but these errors were encountered: