ddfreyne changed the topic of #nanoc to: 3.6.8 (mar 22th) | web http://nanoc.ws/ | repo http://bit.ly/XE6e3G | issues http://bit.ly/VfXaSV | forum http://ho.io/n-discuss | irclog http://irclog.whitequark.org/nanoc
alerante has quit [*.net *.split]
dkm has quit [*.net *.split]
jugglinmike has quit [Quit: Leaving.]
alerante has joined #nanoc
dkm has joined #nanoc
ldk has quit [Ping timeout: 240 seconds]
ldk has joined #nanoc
relix has joined #nanoc
<ddfreyne> bobthecow: fixed the crasher
<ddfreyne> Hmm...
<ddfreyne> Expected: <p>foo&nbsp;bar </p>
<ddfreyne> Actual: <p>foo bar </p>
<ddfreyne> I am inclined to say this is okay. The algorithm only works for at least two spaces.
<ddfreyne> "foo bar baz" would have worked.
<ddfreyne> 7 failures out of 118 now. Not too bad.
<ddfreyne> off to work :)
<ddfreyne> Three failures.
relix has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
gregkare has quit [Ping timeout: 255 seconds]
gregkare has joined #nanoc
relix has joined #nanoc
<francois2> hey, I have done a sprockets datasource, if you are interested: https://github.com/stormz/nanoc-sprockets
<guardian> francois2: what's the use?
<guardian> francois2: I've never understood the need for sprockets while nanoc is a content pipeline by itself
<francois2> guardian, be able to use all the stuff of sprockets, with directives and all, and outputting digest
<guardian> all of which you can achieve with nanoc Rules, filters and erb anyways
<guardian> but well I see how you use it
<francois2> sure
jugglinmike has joined #nanoc
VitamineD1 has quit [Quit: Leaving.]
VitamineD has joined #nanoc
VitamineD has quit [Ping timeout: 252 seconds]
VitamineD has joined #nanoc
VitamineD has quit [Ping timeout: 268 seconds]
VitamineD has joined #nanoc
relix has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
zaiste has quit [Ping timeout: 252 seconds]