12:24 <questiontime> Hey :)

12:24 <questiontime> I was wondering if it is possible to render a site which has relative items?

12:24 <questiontime> Like the item would be relative to each other, so that it would work no matter where it is deployed

12:24 <questiontime> Is this possible?

12:26 <darix> questiontime: https://groups.google.com/forum/#!topic/nanoc/6DSi4jWMaoE

12:26 <questiontime> Thank you so much!

12:27 <questiontime> I was browsing the google group earlier, but I must have missed that!

12:28 <darix> https://www.google.com/search?q=nanoc+relative+paths

12:28 <darix> and it was like the 5th result for me

12:29 <questiontime> Oh :o

12:30 <questiontime> Sorry then, I don't know how I could have missed it :(

18:14 <Evolution> okay, so using the sitemap logic, is it possible to get a list of 'is_hidden' items for a robots.txt to disallow?

18:15 <Evolution> I can't seem to figure out how I'd accomplish this. sitemap lets me do -> <%= xml_sitemap :items => @items.reject{ |i| i[:is_hidden] || i.binary? } %>

18:15 <Evolution> so in theory I should be able to pull some of the same info for robots, right?

18:15 <darix> Evolution: just dont publish hidden items

18:16 <darix> ?

18:17 <Evolution> right. I guess I was hoping to make it a bit more dynamic.

18:17 <darix> you can actually get that list

18:18 <Evolution> how would I go about that?

18:18 <darix> @items.select {|e| e[:is_hidden] }

18:19 <darix> @items.select {|e| e.attributes[:is_hidden] }

18:19 <darix> thats it

19:27 <ddfreyne> no no, don't use e.attributes :)

19:27 <ddfreyne> Just use [] straight away, like in the first example

19:28 <ddfreyne> #attributes should never have been public (it bypasses the dependency tracking)

19:55 <darix> ddfreyne: i think in my case [:something] didnt work

19:55 <darix> but i can try again

20:02 <ddfreyne> darix: lies!

20:03 <darix> ddfreyne: after i had dinner i will try again

20:29 <ddfreyne> darix: https://github.com/nanoc/nanoc/issues/326

20:30 <darix> evil! on purpose breaking my rules file!:p

20:33 <ddfreyne> Well... you shouldn't have used it in the first place ;)

20:33 <ddfreyne> Maybe I'll just emit a warning.

20:33 <stbuehler> you shouldn't have allowed it in the first place :P

20:34 <ddfreyne> Myeah, and #attributes is even public. Ugh

20:37 <ddfreyne> I guess I'll just have to stick to emitting a warning

20:48 <Evolution> ddfreyne: could you elaborate a bit on what you're suggesting?

20:48 <Evolution> for 'just use [] straight away'

20:49 <Evolution> pretend I went to public school and have a terrible grasp of ruby.

20:49 <darix> Evolution: instead of e.attributes[:is_hidden]

20:49 <darix> Evolution: use e[:is_hidden]

20:49 <darix> and public school is no excuse not to learn

20:49 <Evolution> oh I'm fine with learning.

20:50 <Evolution> just not great at it for some things.

23:04 <jachymko> why does nanoc throw CannotCreateMultipleSnapshotsWithSameName when creating two snapshots with the same *contents*?

23:04 <jachymko> snapshot :asnapshot

23:04 <jachymko> e.g. snapshot :a; snapshot :b

23:06 <julian37> hi! a few months ago I made a page with nanoc and got everything working... including cache busting, gzip compression, compass integration and all sorts of neat stuff

23:08 <julian37> now I want to add i18n and I'm really struggling getting the Rules right. anybody around who could give me a hand? basically, I'm trying to generate foo/en/index.html and foo/de/index.html out of the same source file foo.haml, each time with a different setting for I18n.locale

23:08 <julian37> a few months back I had a full mental model of how it all fits together, compile-vs-route wise

23:09 <julian37> but I think it has faded rather quickly

23:11 <julian37> I've added rules to the effect of 'route "/foo/#{locale}/", :rep => :"locale_#{locale}"' but nanoc compile doesn't seem to want to pick them up

23:12 <julian37> can somebody remind me how I'd go about the basic parts: ensuring *that* a file "foo/en/index.html" is generated. I'm pretty sure that once I'm at that point I'll figure out *how* it is going to get generated

23:30 <jachymko> so you want to have one source item? then simply make "route '*', :rep => 'locale_en'" and "compile '*', :rep => 'locale_en'" rules

23:30 <jachymko> and for every other lang

23:31 <julian37> right... sounds simple enough. sorry, it's been a while. thanks

23:32 <julian37> jachymko: if I want to combine the locale rep with a gzip rep, do I just use a Ruby array?

23:34 <jachymko> i don't know. perhaps there's a way of generating rules programmatically, but if there isn't, you will need to have both gzip and normal rep for every language

23:34 <jachymko> :rep => :lang_en …. :rep => :lang_en_gz

23:35 <julian37> ok