vim-ruby-debugger style breakpoints with Pry in Vim

Question

Right now, when I want a breakpoint in vim or Sublime Text, I drop a line like the following into the code:

binding.pry if Rails.env.test?

Pry (and its associated plugins) provide a nice environment in which to do interactive Ruby debugging from the command line.

However, adding actual code to my projects to create each breakpoint (and remembering to remove such code when I make commits) can be cumbersome.

I love what vim-ruby-debugger does in terms of dropping a visual breakpoint into the editor without actually modifying my project's source code, but I've had some trouble getting this to function in the context of my specs (and I'd really prefer to just use Pry 'breakpoints' in the first place).

So the question is, is it possible to drop a binding.pry reference into a file such that an editor like Vim (or Sublime Text, etc.) will pick it up and respond appropriately at debug-time without the line actually be included in the source code?

you'd have to write a script to talk between pry & vim. Using vim --remote-expr you can achieve the same. — Dhruva Sagar
– Dhruva Sagar, Commented Jun 5, 2013 at 4:07
do you want pry-debugger style breakpoints - with navigation and all? (I'm guessing you do) or do you really just want to drop a pry in there? — prater
– prater, Commented Jan 26, 2014 at 8:52

Dave Powers · Accepted Answer · 2019-03-18 18:01:35Z

3

You can use a Git Hooks to prevent a bad commit, like leaving a binding.pry in your code.

This article explains how to do it https://launchacademy.com/blog/automatically-prevent-bad-git-commits

Here you are another good post about it http://www.ryanmcg.com/2013/8/12/another-forgotten-binding-pry/

Also I totally agree that PRY is an exceptional Gem.

edited Mar 18, 2019 at 18:01

Dave Powers

2,4332 gold badges38 silver badges39 bronze badges

answered Feb 22, 2014 at 20:32

Rafa Paez

4,87023 silver badges35 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Dave Powers · Accepted Answer · 2019-03-18 18:22:46Z

2

I'm not aware of any editors or editor plugins that allow you to use Pry by setting breakpoints without actually adding a binding.pry invocation to your source code.

I think the closest solution to your ask would be to use a plugin like vim-infer-debugger, which provides functions to automatically insert debugging statements based on the current filetype. An additional benefit of this plugin is that there's also a command to remove debugger statements, which you could map like so:

nmap <Leader>d :call RemoveAllDebuggers()<cr>

Combined with Git hooks, as mentioned in other answers, this should make it easier to ensure that debugger calls don't get left in your code.

answered Mar 18, 2019 at 18:22

Dave Powers

2,4332 gold badges38 silver badges39 bronze badges

Comments

Dhruva Sagar · Accepted Answer · 2013-06-05 04:09:35Z

0

http://www.vim.org/scripts/script.php?script_id=4451 seems to solve what you want. I haven't tried it personally, but I am going to :).

answered Jun 5, 2013 at 4:09

Dhruva Sagar

7,3351 gold badge29 silver badges35 bronze badges

1 Comment

user456584 Over a year ago

I'm aware of ruby_pry.vim, but I haven't seen evidence that it can do what I describe above.

jmoon90 · Accepted Answer · 2013-12-28 20:34:34Z

0

First off, PRY is an amazing tool and I am glad you found it.

is it possible to drop a binding.pry reference into a file ... without the line actually be >included in the source code?

You need to drop a binding.pry directly in the source code for it to go into pry to test and play around. FYI if you drop a binding.pry into your spec file it will open pry IN the spec file not what it refers to.

You can try better_erros with binding_of_caller and when you run a failing rails server, a) it gives you a better error feel and gives you a direct pry box to the error.

answered Dec 28, 2013 at 20:34

jmoon90

3394 silver badges17 bronze badges

Comments

lsaffie · Accepted Answer · 2014-02-22 20:24:16Z

0

I don't use pry when debugging, I just use the regular debugger if I must. However, here's my vim workflow.

I have vim macro saved "@d" that inserts the following code under whatever line I'm in require 'debugger';debugger;0 This makes it very easy to insert.
To avoid committing debugger lines, I have setup a git hook (pre-commit) that checks if the commit includes these lines (grep)

http://mark-story.com/posts/view/using-git-commit-hooks-to-prevent-stupid-mistakes

answered Feb 22, 2014 at 20:24

lsaffie

1,8241 gold badge18 silver badges24 bronze badges

Collectives™ on Stack Overflow

vim-ruby-debugger style breakpoints with Pry in Vim

5 Answers 5

Comments

Comments

1 Comment

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

Comments

Comments

1 Comment

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related