13:04 <tom[]> i'm using grunt to copy nanoc output somewhere. and i want to use guard to watch and nanoc compile. is it ok to grunt-watch the nanoc output dir? or should i preferably kick off a grunt-copy from nanoc after a compilation in which something changed?

13:19 <bensonshaji> Hi, Can anybody help me? https://groups.google.com/forum/#!topic/nanoc/X4Ti7VYkX1I

13:23 <VitamineD> bensonshaji: don't ask to ask, just ask (and stay around)

13:24 <VitamineD> I'm busy though, but there are other regulars who will answer

13:25 <bensonshaji> VitamineD, I have posted a topic in google groups. Should I post it here again?

13:26 <bensonshaji> Ok.... Here is the question: How can I paginate each category page?

13:26 <bensonshaji> I have a function :

13:26 <bensonshaji> def posts_with_category category

13:26 <bensonshaji> posts.select {|post| post[:categories] && post[:categories].include?(category)}

13:26 <bensonshaji> And I would like to paginate these category pages as "category/topic/1/" "/2/" .... etc

13:26 <bensonshaji> end

13:26 <bensonshaji> How do i do it?

13:35 <guardian> do you commit your Gemfile.lock for nanoc projects?

13:36 <tom[]> guardian: i do. but i don't know if it's a good idea

13:38 <tom[]> thinking about it, if you run bundle manually when needed rather than as part of your automatic build, then i guess it makes sense to commit it

15:23 <bensonshaji> How can I paginate each category page?

15:32 <guardian> there's http://nanoc.ws/docs/guides/paginating-articles/ you can build from

15:33 <guardian> bobthecow: I think we once discussed about the best way to load settings from a file that's not nanoc.yaml. Does it ring a bell?

18:53 <ddfreyne> guardian: I commit my Gemfile.lock

18:54 <ddfreyne> tom[]: watching output/ and copying from there i fine

18:54 <tom[]> ddfreyne: done. thanks

18:56 <guardian> ddfreyne: ok

18:56 <guardian> that's what I settled on as well

18:58 <ddfreyne> guardian: That way, other people can check ou tyour project, run bundle install, and not worry about dependency problems

18:58 <ddfreyne> (Or wrong versions that have incorrect results etc)

19:01 <guardian> ddfreyne: what are my options to have settings loaded globally outside of nanoc.yaml?

19:01 <guardian> ddfreyne: a class that loads my own .yaml file?

19:02 <ddfreyne> guardian: I'd suggest using a preprocessor block that loads it and merges it with @config

19:04 <guardian> ah yeah that's an option I also considered

19:10 <guardian> ddfreyne: do you remember my idea of building the documentation of several products using the same nanoc "framework". I had to that project aside for a while, but here is the sum of what I discussed with bobthecow: http://pastebin.com/Xk8CZvb0

19:11 <guardian> ddfreyne: each product has a nanoc site, and there's a _factory submodule which is the framework

19:11 <guardian> ddfreyne: and now I'm experimenting with the idea so that Rules includes _factory/Rules

19:12 <guardian> ddfreyne: in product/lib/whatever.rb I would populate helpers from _factory/lib/**.rb the same way nanoc compiler does

19:14 <guardian> ddfreyne: this would permit each product to customize things a bit, yet I still need to brush out details about the preprocess phase and the fact that content and layouts can be potentially in both product/content product/layout or _factory/content/ or _factory/layout

19:30 <bobthecow> tom[] guardian: rule of thumb with lockfiles is never commit them for libraries, always commit them for projects.

19:33 <guardian> bobthecow: o/

19:33 <bobthecow> hey

19:33 <bobthecow> did you sort your config thing?

19:34 <guardian> I'm working on it

19:38 <guardian> bobthecow: I like your idea of each product having its own nanoc site, deferring defaults to a _factory submodule

19:39 <guardian> bobthecow: I'm in the process of plumbing things together

19:51 <guardian> bobthecow: it would be easier if the filesystem_unified data source had a configurable prefix

19:51 <guardian> bobthecow: I would add another filesystem_unified that populates items from _factory/content and layouts from _factory/layout

19:56 <guardian> ddfreyne: would it be acceptable to have content_prefix and layouts_prefix as part of filesystem's configuration? if I submit a patch that does so, would you accept it?

20:02 <guardian> bobthecow: also I'm going to keep compass along with bootstrap-sass because it brings nifty tools like inline-image() one could use to override/customize bootstrap styles

20:57 <guardian> how to make YARD format these properly? https://github.com/nanoc/nanoc/blob/master/lib/nanoc/data_sources/static.rb#L20-22

20:57 <guardian> see http://nanoc.ws/docs/api/Nanoc/DataSources/Static.html

21:40 <ddfreyne> guardian: Such a patch is already in nanoc 3.7

21:43 <ddfreyne> guardian: One problem with loading lib/ code from elsewhere is that it may trip up the outdatedness check

21:44 <ddfreyne> guardian: if you have a data source that loads items/layouts from elsewhere, that is fine

21:45 <ddfreyne> Hmmm...

21:45 <ddfreyne> nanoc 3.7 does not have a configurable name, interesting.