00:30 <bobthecow> before that runtime error, it was causing problems but not letting people know. so this is at least a step better :)

07:39 <guardian> o/

08:59 <ddfreyne> Hi

15:20 <guardian> ddfreyne: when nanoc compile -V says "identical", it's because it has recompiled an item THEN noticed it's identical right?

16:26 <VitamineD> guardian: yes

16:39 <guardian> then I'm still witnessing strange behaviors from time to time

16:39 <guardian> show-data telling me nothing is outdated

16:39 <guardian> but compile -V compiling things

18:20 <dkm> I'm noticing an odd (to me) behavior in error reporting in nanoc 3.7.2: when I erroneously have multiple content files with the same name nanoc is crashing with an error in a filter library

18:21 <dkm> it's an extension to the kramdown filter, and it's the 'add_parser' lines that add my custom parser to kramdown's parser list

18:22 <dkm> if I comment out all those lines then I get the expected 'two content files with the same name error'

18:22 <dkm> any ideas on whats going on and how I can get more useful error reporting?

18:28 <bobthecow> what's the error say?

18:39 <dkm> "RuntimeError: A parser with the name asides already exists!" at https://github.com/hazybluedot/hazyblue.me/blob/master/lib/dkramdown.rb#L37

18:40 <dkm> and then if I comment that line, the next 'define_parser' at 59

18:40 <dkm> so maybe it's a weird issue with kramdown's define_parser method

18:50 <bobthecow> try wrapping the whole file in `unless defined?(Kramdown::Parser::DKMramdown); ... end`

18:53 <dkm> bobthecow: oh, is this a 'nanoc makes two passes' kind of issue?

18:53 <bobthecow> that's my guess.

18:54 <bobthecow> for most things it doesn't matter, but apparently kramdown's not a fan.

18:55 <dkm> ok, yep, wrapping it in 'unless ... end' fixed it

18:55 <bobthecow> nice.

18:55 <bobthecow> it might make sense to have something about that in the docs somewhere.

18:57 <bobthecow> ddfreyne: poke. ^ ;)

18:58 <dkm> yeah, it was pretty frustrating when I was trying to debug what I thought was a problem with my kramdown parser code!

18:59 <dkm> which I knew had been working before and hadn't changed (I thought maybe there was a version change in kramdown that broke something)

18:59 <bobthecow> it'd be rad if nanoc 4 didn't double-load lib files.