2 ms·
I find pry, pry-debugger, pry-remote etc. much better than RubyMine's debugger in practice. I found IDE debug setup to be quite fiddly, as a lot of our app need
by barrkel 13y ago
I find pry, pry-debugger, pry-remote etc. much better than RubyMine's debugger in practice. I found IDE debug setup to be quite fiddly, as a lot of our app needs other bits - Java, C++, queuing, mock smtp, etc. to be in place at the right time.
I used RubyMine for 8 months before switching to emacs. I was more productive after 6 weeks in emacs than 6 months in RubyMine.
Emacs' robe integrates with pry to do symbolic lookup of definition (I guess that's what you mean by "method click-through"). It works especially well when you're browsing symbols created through metaprogramming. But I don't normally use it, I normally use helm-git-grep, often initialized with text from the cursor. This package changed the way I worked - it's instantaneous incremental grep from across your whole repository.
Much of the app I work on is written in CoffeeScript and Backbone. Instantaneous lookup of message strings made whole chunks of the app almost trivial to work with, whereas they were a chore before.
I don't code languages like Ruby in anything like the same way I write C or Java. I find Ruby is best written in an in-context REPL, where the results can be interactively seen. I then look at the command history and pluck ou the bits I want to keep, and refactor them. Emacs REPL buffers work very well for this too.
The ability to write a mode hook that binds a key to a function that's especially handy in that mode - or even bind a key to a lambda that only needs to work in the current session - is killer though. Binding keystrokes through UI is a complete PITA, and it always feels like a dodgy investment, because you don't know how easily or reliably you'll be able to export it or import it onto the next version or next job. Whereas the investment I put into emacs feels like it'll last me decades.