08:10 <guardian> o/

12:17 <guardian> duh

12:17 <guardian> what should I do with this comment? https://github.com/nanoc/nanoc/pull/463#issuecomment-49597727

12:20 <prxq> looks like a mistake operating the comment form

12:28 <guardian> maybe

12:46 <guardian> ddfreyne: would you agree with adding a setting that tells nanoc where to look for custom commands?

17:11 <Tobia_Tesan> Hi, excuse me − what would be a correct way of declaring a global variable, like my site′s title ("My Awesome Recipes" or something like that) and then recall that in layouts/content pages? Thanks!

17:12 <Tobia_Tesan> I tried defining a global variable in default.rb but can′t seem to recall it.

17:15 <alerante> Tobia_Tesan: you can define it at the top level of nanoc.yaml and refer to it as @config[:varname]

17:37 <Tobia_Tesan> Sorry again − is there some sort of autoslugify function I can use in the routing rules? Something like route "*" do∖ item.identifier = item[:year]+item[:month]+slugify(item[:title]) ? 

18:08 <bobthecow> Tobia_Tesan: no, but ruby has one :)

18:08 <bobthecow> Tobia_Tesan: https://github.com/rsl/stringex

19:26 <guardian> git status

19:26 <guardian> oops :)

20:51 <guardian> hmm what's a nanoc plugin?

20:57 <bobthecow> there's no "plugin" in the sense of, say, browser plugins. it's just a thing that works with nanoc.

20:57 <guardian> yeah in fact nanoc calls plugins data sources or filters

20:58 <guardian> there's something I quite don't get: https://github.com/nanoc/nanoc/pull/407

20:58 <guardian> when to call Nanoc::CLI.after_setup ?

20:58 <guardian> which file should I write so that I get to register a new command through Nanoc::CLI.after_setup ?