Debugging Ruby in 2025? @st0012's got your back.

https://railsatscale.com/2025-03-14-ruby-debugging-tips-and-recommendations-2025/

@lucian I don't think there's a command to achieve this atm.
What I usually do is:
- Run `bt 15` to see the closest frames, or `bt /regexp/` if I know the path of the frame I'm looking for
- Run `f [frame_id]` to move there

It's still 2 more extra steps but may be more efficient in some cases 🙂

BTW I now mostly move to Bluesky and only check here sparsely.

As his wife I think the thing that would thrill him the most is if there could be a scholarship in his name at Ruby conferences. All the full price people can kick in an extra $10 each and then some people who otherwise wouldn't be able to go can come and learn.

His life's mission was to help people access information and learning.

🎙️New Episode of Code and the Coding Coders who Code it! Episode 43 with @st0012

https://podcast.drbragg.dev/episodes/episode-43-stan-lo

#ruby #Rails #code #coding #coders #podcast

@Schneems By style changes, do you mean the extra `nil` and the different prompt `irb(main):001:0>`?

It looks like the programmatic version runs an older version of IRB (e.g. the one bundled with Ruby 3.3) where the manual version runs the IRB released as a gem.

@Schneems it’s a bigger work than adding these incremental improvements.

Let’s give Ruby’s English documentation new homepages! If this is accepted in time, it’ll be applied to the upcoming Ruby 3.4 documentation. We can then explore ways to backport similar changes to older Ruby versions.

The current homepage just shows the project’s readme, which is less helpful than a dedicated page in most cases.

PR: https://github.com/ruby/ruby/pull/12227

@kerrick thanks for the detailed feedback and indeed that’s an issue.
Here’s how I think we can improve it:
1. Focus on improving the current master documentation, which will become 3.4’s doc in a month.
2. After 3.4 is out, we develop a process to backport documentation with branch maintainers. (Ruby 3.2 and 3.3 are maintained by different Ruby committers, for example)

I wrote something about Ruby’s documentation. If you’re at #RubyConf this week and want to improve it together, come talk to me 🙂

https://st0012.dev/a-rdoc-maintainer-s-view-on-ruby-s-documentation

Thanks to @thomasmarshall and @hsbt's help, docs.ruby-lang.org now has favicon 😄

@eightbitraptor That's a great suggestion. But I won't be able to do that this week as I need to focus on something else.
Can you please open an issue so we don't forget about it later 🙂

https://github.com/ruby/rdoc/issues

And for issue reports and feature requests, please open them in https://github.com/ruby/rdoc/issues

Thanks!

For the first time, https://docs.ruby-lang.org/en/master is now using red 🔴 instead of green 🟢, and with more selective highlighting.

Like the previous update, this isn’t final either. We plan to make incremental, continuous improvements to RDoc and http://docs.ruby-lang.org 😄

@zenspider Make a PR yourself 🤷‍♂️

Red-themed RDoc and docs.ruby-lang.org?
PR: https://github.com/ruby/rdoc/pull/1191

Has anyone noticed some functional improvements I recently shipped to https://docs.ruby-lang.org/en/master 😉

@stevenharman It does have a whereami command though. Maybe try the latest version of it?

Alternatively, to get a better REPL experience, you can set `RUBY_DEBUG_IRB_CONSOLE=1` to make ruby/debug use IRB as its REPL.

026: Exploring Rails' Default Debugger with Stan Lo

https://www.railschangelog.com/26

Discussions: https://discu.eu/q/https://www.railschangelog.com/26

#programming #rails #ruby #webdev

@getajobmike Thank you for sharing it 🙌

I bet every Ruby developer in the world can improve their debugging skills by watching this talk. @st0012 has done some great work on Ruby over the last few years.

https://www.youtube.com/watch?v=gseo4vdmSjE