Tossing Out IRB for Pry(philaquilina.com) |
Tossing Out IRB for Pry(philaquilina.com) |
There's a brief Railscast on it as well: http://railscasts.com/episodes/280-pry-with-rails
Incidentally, because I want syntax-highlighting for ruby, I have this in my ~/.irbrc
def vim
edit_interactively("vim -c 'set ft=ruby'")
end
[1] - https://github.com/jtrupiano/flyrb;)
[19] (pry) main / Pry: 1> cd ..
[20] (pry) main / Pry: 0>
Shouldn't 'cd..' take you out of the Pry scope?Should look like this: [20] (pry) main: 0>
I think Pry is great, I wrote a little console with it recently for a simple back-end app, and the edit feature looks like your most advanced option for this kind of thing. But for the sake of accuracy, it's not actually 100% brand new functionality. A lot of people have been doing that in IRB for a long time.
Other things the Pry editor feature can do that i haven't seen elsewhere: it can edit methods (`edit-method MyClass#my_method`), it can open up an editor directly on the file/line that caused the last exception (`edit --ex`), it can edit previous expressions (`edit -i EXPR`).
Your interactive_editor gem was inspiration for this though, a very nice little gem :)
If I was in a sportsbar and heard someone dissing the NFL, I wouldn't think "What do they have against the National Forensics League?"
On HN, if you see an acronym where it doesn't make sense to you, great! Most likely you're being presented the opportunity to learn about some cool technology.
Opening the URL made it obvious what it was referring to, however. And then I immediately installed the package to try it out.