-
Notifications
You must be signed in to change notification settings - Fork 120
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
EVAL_HISTORY is busted #774
Comments
Do you think IRB needs type validation for configs? These are some other confusing configs and invalid values that raise error. IRB.conf[:IRB_NAME] = :ruby # should be string
IRB.conf[:IRB_RC] = '/path/to/.irbrc' # should be proc
IRB.conf[:BACK_TRACE_LIMIT] = ENV['IRB_BT_LIM'] # should be number
IRB.conf[:PROMPT] = '>> ' # should be hash |
Yeah both type validation and better documentation (discovery) are needed for those configs.
For this we should also support symbol, or even anything that responds to
|
That's totally on me. I should have noticed that some default values were nil and some were not. I don't think we need full type checking, but some defensive programming would be nice... and doco. always doco |
@st0012 want me to file a separate bug against doco and type checking? |
@zenspider Sorry for the delay. I've now cleared other priorities and will start looking at this. For the start I'll target the configs listed here, so feel free to add new ones. |
Actually, I think I'll close this with #953. If you find other configs can use the same improvement, please open new ones 😄 |
#953 feels like the right thing to do. Thanks! |
with
IRB.conf[:EVAL_HISTORY] = true
everything is busted:even
irb_info
current .irbrc:
The text was updated successfully, but these errors were encountered: