Nil config items cause execeptions by not causing use of default values
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 311
- Forks
- 99
- Avg merge
- 6d 4h
- Merged PRs (30d)
- 1
Description
Description
When I set certain options, Readline would set them to default values, but not Reline:
::Readline.input = nil # Should set input to $stdin
::Readline.output = nil # Should set output to $stdout
::Readline.special_prefixes = nil # Should set to empty string ''
What are your expected behavior and actual behavior of your environment?
In Reline, these seem to keep and use the nil value, raising errors. I would expect it to behave the same as Readline if it aspires to be a drop-in replacement for it.
The above are those I've stumbled across. Should see that all config options get the Readline default when set to nil.
Terminal Emulator
What's your terminal emulator?
KDE's konsole, but this is independent of the emulator.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing Reline's configuration behavior for input, output, and special_prefixes with the corresponding Readline defaults. Check how nil is handled for each configuration option, then verify that nil uses the expected default values without raising errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100