rerun the previous command with corrected spelling in irb.

[krsinghshubham]

as a Feature request when in IRB when did_you_mean throw us a error , can we run something to re-run the previous command with corrected spelling.
Something like how https://github.com/nvbn/thefuck does this ?
If it sounds good and get a feature-request tag i can work on this to create a PR.

[yuki24]

Thanks for your request! The language of the library isn't really appropriate, but I think it would be interesting to see a keyboard shortcut that is available on irb, that automatically replaces the code hunk that causes a NoMethodError. We should be able to detect where to fix with error_highlight, and we could probably pick the closest match, if and only if there is only one match with the edit distance <= 2.

[krsinghshubham]

@yuki24 I originally implemented this in PR #204 in this repository, but have since moved the implementation to the IRB gem in ruby/irb#1174.

Why this belongs in IRB:

• Load order: did_you_mean is a default gem loaded at boot, while IRB is loaded later, for example in the Rails console. When did_you_mean loads, IRB may not yet be available, so the extension never activates and the fix command does not work in Rails console.
• Ownership: fix is an IRB command, similar to exit, load, or help, so it logically belongs to the REPL layer.
• Context: IRB already owns the eval loop, exception handling, and access to the last executed code, which are all required to implement this feature correctly.
• API usage: The IRB implementation uses only the public did_you_mean API, such as #corrections and DidYouMean::Levenshtein, with no patching or extension hooks.
• Separation of concerns: did_you_mean remains responsible for spell checking, while IRB handles REPL behavior.

The IRB PR is ready for review: ruby/irb#1174.

[yuki24]

@krsinghshubham Interesting approach! I'll take a look and respond on the irb issue.