<ddfreyne>
bobthecow: One of the mistakes I made in nanoc 3.x is to emulate some of the "bundle" behavior
prxq_ is now known as prxq
relix has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
jugglinmike has joined #nanoc
<jugglinmike>
Is it possible to run only some subset of nanoc's test suite?
<jugglinmike>
Doesn't look that way, but I can make some quick-and-dirty changes to test.rake just to speed things up for myself during development
relix has joined #nanoc
<guardian>
hi
<guardian>
ddfreyne: I would like to start a new project, should I stick to nanoc 3.x?
<guardian>
I have another question. bobthecow mentioned pry again. I never used it. How do you use it in the context of nanoc? you add require 'pry' in the helper or filter you're trying to debug then what?
VitamineD has quit [Quit: VitamineD]
VitamineD has joined #nanoc
<bobthecow>
guardian: require 'pry' anywhere, then call `binding.pry` wherever you want to debug.
<bobthecow>
that's the equivalent to the `debugger` command in javascript.
<bobthecow>
so i have a code snippet in my editor: `require 'pry'; binding.pry`