Michael Guterl wrote: > Marnen Laibow-Koser wrote: >> Ralph Shnelvar wrote: >>> newbie here ... >>> >>> I am tracing logic putting puts and logger.info calls in my code. >>> >>> I _think_ Rails is buffering output so that I can't see what happens >>> until I close out webrick. >> >> But you are probably wrong. If you watch the log scroll by, you will >> generally see puts and logger output immediately. >> >>> >>> How do I tell Rails (or whatever) that output is not to be buffered? >> >> You should not need to. >> >> Also, get familiar with ruby-debug and test-first development. These >> two things will drastically reduce your need for logging. >> > > Dude, don't be such a dick. Logging doesn't necessarily have to do with > debugging or test-first development.
I'm aware of that, and even if I were not, that's no reason for name-calling. You owe me an apology. Best, -- Marnen Laibow-Koser http://www.marnen.org mar...@marnen.org > > Best, > Michael Guterl -- 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 rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
