Skip to content

IRB.conf[:SAVE_HISTORY] should handle boolean values#1062

Merged
tompng merged 1 commit into
masterfrom
fix-#1058
Jan 11, 2025
Merged

IRB.conf[:SAVE_HISTORY] should handle boolean values#1062
tompng merged 1 commit into
masterfrom
fix-#1058

Conversation

@st0012

@st0012 st0012 commented Jan 11, 2025

Copy link
Copy Markdown
Member

Although not documented, IRB.conf[:SAVE_HISTORY] used to accept boolean, which now causes NoMethodError when used.

This commit changes the behavior to accept boolean values and adds tests for the behavior.

Closes #1058

Although not documented, `IRB.conf[:SAVE_HISTORY]` used to accept boolean,
which now causes `NoMethodError` when used.

This commit changes the behavior to accept boolean values and
adds tests for the behavior.
@st0012 st0012 added the bug Something isn't working label Jan 11, 2025
@st0012 st0012 mentioned this pull request Jan 11, 2025
@tompng tompng merged commit 8b1a07b into master Jan 11, 2025
@tompng tompng deleted the fix-#1058 branch January 11, 2025 14:03
matzbot pushed a commit to ruby/ruby that referenced this pull request Jan 11, 2025
(ruby/irb#1062)

Although not documented, `IRB.conf[:SAVE_HISTORY]` used to accept boolean,
which now causes `NoMethodError` when used.

This commit changes the behavior to accept boolean values and
adds tests for the behavior.

ruby/irb@8b1a07b2a8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Disable save history

2 participants