rspec users - May 2010 - Kernel#debugger reminder method is unhelpful

I''m not exactly sure what the motivation behind the
"debugger" catch was,
perhaps a convenience method to allow your code to remain littered with
debugger statements? At any rate, it''s obstructed my normal use of
ruby-debug, and regardless of whether I''ve passed the -d or --debug
flag, it
still complains that the debugger is ignored unless if I use the rdebug
wrapper.


require ''ruby-debug''; debugger # <- does not work under
rspec 2.0,
regardless if -d or --debug was provided

# ^ This is how you use the debugger with spork, effectively
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/rspec-users/attachments/20100503/cde383a3/attachment.html>

Actually, now that I think about it, Spork claims the Kernel#debugger method
before Rspec checks if it should install it''s catch, so it might be
fine.

Still, I would prefer if if the above "require
''ruby-debug''; debugger"
convention still worked.

Tim

On Mon, May 3, 2010 at 12:35 PM, Tim Harper <timcharper at gmail.com>
wrote:
> I''m not exactly sure what the motivation behind the
"debugger" catch was,
> perhaps a convenience method to allow your code to remain littered with
> debugger statements? At any rate, it''s obstructed my normal use of
> ruby-debug, and regardless of whether I''ve passed the -d or
--debug flag, it
> still complains that the debugger is ignored unless if I use the rdebug
> wrapper.
>
>
> require ''ruby-debug''; debugger # <- does not work
under rspec 2.0,
> regardless if -d or --debug was provided
>
> # ^ This is how you use the debugger with spork, effectively
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/rspec-users/attachments/20100503/f599ef30/attachment-0001.html>

On Mon, May 3, 2010 at 12:37 PM, Tim Harper <timcharper at gmail.com>
wrote:
> Actually, now that I think about it, Spork claims the Kernel#debugger
> method before Rspec checks if it should install it''s catch, so it
might be
> fine.
>
> Still, I would prefer if if the above "require
''ruby-debug''; debugger"
> convention still worked.
>
> Tim
>

This patch resolves the issue:

http://github.com/timcharper/rspec-core/commit/c476e088ebabb4a89c8566be4fa07849d88271ac

Here is a related bug report:

http://github.com/rspec/rspec-core/issues/#issue/24
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/rspec-users/attachments/20100503/7792e59b/attachment.html>