Can't escape from eval with next

[sam452]

I believe I've followed the steps to plug in pry-nav into my Gemfile in Rails. As a plug-in to pry, I'm unaware of anything else to do but 'next' yields this syntax error. 'step' yields undefined local variable for 'step.' I've found nothing else on Google of what I'm missing.

[nixme]

What versions of pry and pry-nav are locked in your Gemfile.lock?

Also, if you're using ruby 1.9.2, 1.9.3, or 2.0, you should switch to pry-debugger https://github.com/nixme/pry-debugger

[sam452]

Oh, thanks for asking:

pry (0.9.12.1)
coderay (> 1.0.5)
method_source (> 0.8)
slop (> 3.4)
pry-nav (0.2.3)
pry (> 0.9.10)
pry-remote (0.1.7)
pry (> 0.9)
slop (> 3.0)
pry-stack_explorer (0.4.9)
binding_of_caller (>= 0.7)
pry (~> 0.9.11)

thx, sam

On Jun 5, 2013, at 7:39 PM, Gopal Patel [email protected] wrote:

What versions of pry and pry-nav are locked in your Gemfile.lock?

Also, if you're using ruby 1.9.2, 1.9.3, or 2.0, you should switch to pry-debugger https://github.com/nixme/pry-debugger

—
Reply to this email directly or view it on GitHub.

[nixme]

How are you running pry? via binding.pry inside some code while your app server is running? Or by running "pry" from the shell. If the latter, are you running through a bundler-aware mechanism? e.g. "bundle exec pry" or if you've binstubbed it "bin/pry" in the root of your project?

[sam452]

This may be a repost from earlier.
I'm running

binding.pry

inside my create method in my Rails app.
Since I'm running 1.9.3 I ditched the

pry-nav

in favor of

pry-debugger

. I bundle install and update. I was surprised to find the same error. Here is my updated Gemfile.lock:

pry (0.9.12.2)
  coderay (~> 1.0.5)
  method_source (~> 0.8)
  slop (~> 3.4)
pry-debugger (0.2.2)
  debugger (~> 1.3)
  pry (~> 0.9.10)
pry-remote (0.1.7)
  pry (~> 0.9)
  slop (~> 3.0)
pry-stack_explorer (0.4.9)
  binding_of_caller (>= 0.7)
  pry (~> 0.9.11)

[rdaniels]

I'm having this same issue when i run RSpec with a binding.pry in the code:

[2] pry(#<ShippingQuote::Shipping>)> next
SyntaxError: (eval):2: Can't escape from eval with next

[nixme]

Unfortunately, somehow the ruby "next" keyword is getting invoked instead of the pry command. Can you try adding an alias for next: Pry.commands.alias_command 'n', 'next' and then running n instead?

[ndavis]

Pry.commands.alias_command 'n', 'next' RuntimeError: Command: 'next' not found from /usr/local/var/rbenv/versions/1.9.3-p545/lib/ruby/gems/1.9.1/gems/pry-0.9.12.2/lib/pry/command_set.rb:216:in 'alias_command'

[toppsdown]

Seeing the same issue:

next
SyntaxError: (eval):2: Can't escape from eval with next

Pry.commands.alias_command 'n', 'next'
RuntimeError: Command: next not found
from /Users/Ethan/.rbenv/versions/1.9.3-p484/lib/ruby/gems/1.9.1/gems/pry-0.9.12.2/lib/pry/command_set.rb:216:in `alias_command'

[b-raines]

Had this same issue for the past month and still haven't figured it out.

[matthewbga]

Ditto here.

[mitchcail]

ya me too

[lilliealbert]

Ditto.

[stephan-nordnes-eriksen]

+1

[stephan-nordnes-eriksen]

Might have figured it out: In my case I was using "require 'pry'". But since I was running ruby 2.0+ I needed to use require 'pry-byebug'.

In other words: you might be using the wrong version of pry to ruby.

Ruby 1.9.2/1.9.3 => https://github.com/nixme/pry-debugger
Ruby 2.0+ => https://github.com/deivid-rodriguez/pry-byebug

[Kshitij-Banerjee]

In my case, pry did not have the next command and was using the ruby method.

check that next command is present in Pry.commands

[omgreenfield]

I have switched to pry-debugger and it was also throwing this error.

I checked Pry.commands during execution and like @Kshitij-Banerjee pointed out, I didn't have the 'next' or 'step' commands.

I added gem 'pry' and gem 'pry-debugger' (even though nowhere in the documentation did it suggest this). Ran a bundle install, and when I ran Pry.commands again, next was there! And next indeed worked!

[Kshitij-Banerjee]

@GosuSheep nice.

[mpelzsherman]

Hit the same issue with ruby 2.2.1. Replacing gem 'pry' with gem 'pry-byebug' worked for me.

[matthewbga]

Yes, same here.

[xasos]

+1