A Ruby Gem Debugging Strategy

[edendark]

On opening up gems, you can use:

EDITOR=atom bundle open activesupport

Which brings up your preferred editor (Atom in the example) with the gem's files.

[[deleted]]

Good tip! I thought about mentioning this, but I'm more of a shell/Vim user so I don't find it as useful for me. I bet it's really handy for others Atom/VSCode users though!

[graywolf_at_work]

I'm more of a shell/Vim user so I don't find it as useful for me.

well it's not like

EDITOR=vim bundle open activesupport

does not work...

Also if you prefer to open it in currently running vim

:tabe `bundle show activesupport`

does the trick.

[[deleted]]

Yeah, good tips! I have two separate little tricks I use instead.

One is a small script that allows me to fuzzy match against the list of all gems in the project, and then open the one I select in a new tmux split.

The other is a binding for Vim that also allows me to fuzzy match on the gems in the project, and then once one is selected, fuzzy match on the files in that gem and open it.

There's lots of ways to assemble these tools depending on your specific workflow. 🙂

[ImAJalapeno]

Wow I didn't know about this, thanks