Matt Jones wrote: > Did that *ever* work? Development mode reloading only works between > requests. Ruby-debug may also be caching its own copy of the source > somewhere.
I think it happens when I open another terminal and use script/console. Well I wasn't able to clearly identify the cause. Another weird behavior, is that when the debugger kicks in, sometimes I can directly access classes and objects without having to go into irb (I think that applies when debugger is in a model), sometimes I need to enter irb. Another one: when entering irb, I sometimes see lot's of error/warning messages, and the request carries on as if the breakpoint didn't exist. If I reissue the request and enter irb, the second time the request won't carry on. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
