03:47 <bobthecow> ctp: you'd have to do it at the server level, since nanoc pages are static.

03:48 <bobthecow> but it's totally doable.

03:48 <bobthecow> what are you using to serve the site?

07:47 <ddfreyne> guardian: nanoc makes no guarantees about ompilation order so that is not possible anyway

07:48 <ddfreyne> guardian: Maybe you can use a (cryptographic) hash instead of an autogenerated id?

08:18 <guardian> ddfreyne: semantically I need: first call to tabs() from item1 => 1, second call to tabs() from item1 => 2, first call to tabs() from item2 => 1

08:19 <guardian> ddfreyne: I can live with a counter that increments each time tabs() is called, whatever the caller. but it's a bit less pretty in the markup but that would be a really minor inconvenience

08:31 <ctp> bobthecow: hi, running nginx here

08:32 <ctp> looking for an oauth2 connector for nginx right now. perfect setup would be oauth2 against github account

19:13 <ics> quick question regarding CompilerDSL#compile: when you pass a :rep to compile, this is where the :rep is defined correct?

19:15 <ics> I am filtering images to create pages for each and to do this am using a custom rep, :single_image_rep for example

19:19 <ics> I was thinking of defining the rep in the filter itself, but now I realize how stupid that sounds. Nevermind...

19:20 <bobthecow> ics: yes, that's where the rep is defined.

19:20 <bobthecow> and no, you prolly shouldn't do reps in filters.

19:20 <bobthecow> you could extend the dsl with a helper for making your reps, maybe.

19:21 <bobthecow> similar to how #passthrough or #ignore just wrap normal calls to #compile and #route

19:22 <ics> thanks. it's been a while since I've worked with nanoc and am in a slight crunch, but that makes sense

19:23 <ics> at least for now, I'm just trying to make things more convenient by compiling custom reps for all binary files

19:24 <ics> and adding a #binary_path method back to the original rep for slightly more convenient templates

19:28 <guardian> ddfreyne: so did is use tabs() usecase clear now? :)