07:37 <ddfreyne> bobthecow: I'd like to merge the nanoc 4 upgrade guide into master ASAP. As soon as I no longer have any major TODOs, I'd like to merge it. Are you OK with that?

07:37 <ddfreyne> This way, I can point people to it and sollicit feedback.

10:44 <timgauthier_> aha!

10:45 <timgauthier_> Hello Nanoc… I am in need of some assistance

10:46 <timgauthier_> Trying out Nanoc for first time. I was able to get nanoc working yesterday with Pygment highlighting (pygment.rb gem) and today when I restarted all of my dev enviroment (mac) and try to build the site it gives me a ruby error. When I coment out the lines with Pygment filtering in the rules file the build succeeds. Help?! (uploading code to github now)

14:55 <ddfreyne> timgauthier_: Are you using bundler?

14:55 <ddfreyne> or were you using bundler?

14:55 <ddfreyne> Are you using rvm/rbenv/chruby?

14:56 <ddfreyne> Also, what Ruby error are you getting? Can you paste it using gist.github.com?

15:06 <timgauthier_> I was using bundler yea

15:06 <timgauthier_> I’ve switched to trying out middleman, but solved this error, it was missing uhm.

15:07 <timgauthier_> nokogiri

15:08 <ddfreyne> Ah yeah, the syntax highlighter requires nokogiri because it needs to parse the HTML and search for <pre> elements to highlight

15:10 <timgauthier_> yeah, but if i had syntax highlighting working the day before, i don’t understand how i broke it to not work the next day. :P

15:10 <ddfreyne> timgauthier_: Did you use it with bundler one day and without the other?

15:11 <timgauthier_> I honestly don’t know, but that could be it.

15:11 <timgauthier_> it must have been it, since it just wasn’t in the gemfile.

15:11 <ddfreyne> timgauthier_: If you exeucte with bundler and the Gemfile doesn't have nanoc, `bundle exec nanoc` will fail with a Nokogiri LoadError

15:11 <ddfreyne> Probably!

15:12 <ddfreyne> Also, I recommend executing `bundle exec nanoc` rather than `nanoc`.

15:12 <timgauthier_> ugh, so many extra characters!

15:12 <ddfreyne> alias be="bundle exec"

15:12 <ddfreyne> be nanoc

15:12 <ddfreyne> It's much more zen, too

15:12 <timgauthier_> its been so many hours of figuring stuff out and switching things around… I can’t even remember why i switched to middleman…

15:13 <VitamineD> alias n='bundle exec nanoc'

15:13 <timgauthier_> haha VitamineD

15:13 <ddfreyne> You could also use guard-nanoc, so you don't even have to run nanoc *at all* :)

15:13 <timgauthier_> alias be is more versitile ;)

15:13 <timgauthier_> yeah, i couldn’t get that working either

15:13 <timgauthier_> I think i went to middleman because its more like jekyll

15:14 <ddfreyne> timgauthier_: Were you getting any specific error?

15:14 <ddfreyne> timgauthier_: I've never tried Middleman, and I have no reason to, because I wrote nanoc :)

15:14 <timgauthier_> hehe

15:15 <timgauthier_> I don’t remember nor have i documented my errors with watch. i think i tried to gem install and had a failure

15:17 <ddfreyne> timgauthier_: You probalby need to add guard-nanoc to the gemfile, run `bundle`, then `be guard`

15:17 <ddfreyne> (having aliased `be` to `bundle exec` first)

15:18 <ddfreyne> I don't think I ever use `gem install` anymore… I use Bundler for everything

15:19 <timgauthier__> It felt like I was going to have to do a lot of overhead in the config to have some pages use templates and others not, and passing variables around. Middleman was suggestinf in #ruby and so far looks like it will be more like jekyll’s syntax for passing variables etc.

15:20 <timgauthier__> I’m sure what you wrote can do that, but i’m not experienced enough with ruby, and the documentation wasn’t enough for me.

15:24 <ddfreyne> timgauthier__: The aim of nanoc is to be the most flexible static site generator out there

15:24 <ddfreyne> And I believe it achieved that goal

15:25 <timgauthier__> cool :)

15:25 <ddfreyne> I am not sure what you mean by passing variables around, though. Rendering partials with specific variables?

15:26 <timgauthier__> yeah. and as I typed out what i was doing i realize I would just need to do it in a different way on nanoc

15:27 <timgauthier__> from the front matter, can you declare the layout? or is that just done from the setting file?

15:27 <ddfreyne> timgauthier__: You can do that by setting "layout: default" in the frontmatter, and then in the Rules file you change the #layout call (which looks like "layout 'default'") to use the item attribute, i.e. layout @item[:layout]

15:28 <timgauthier__> whats the benifit of using the routing like that?

15:29 <timgauthier__> i mean, in the rules file

15:29 <ddfreyne> timgauthier__: The benefit of defining the layout in the Rules file is that you only specify it in a single file

15:29 <timgauthier__> instead of in each file/location?

15:29 <ddfreyne> While still having the ability to specify it in files individually, if you need/want it

15:29 <ddfreyne> Yeah

15:30 <timgauthier__> so you can do exactly like in middleman where you can specify a layout or routing with the file itself or you can do it in the rules file?

15:30 <ddfreyne> Yes

15:31 <ddfreyne> timgauthier__: You can also e.g. set 'path: "/robots.txt"' in the frontmatter and then in the Rules file check whether @item[:path] is not nil, and use that in the routing rule instead of the normal flow

15:32 <ddfreyne> I use that for a few files on the nanoc web site (robots.txt and sitemap.xml, I believe)

15:32 <timgauthier__> the thing i felt and was running into was trying to build the blog portion. My site calls it journal and has that as the address, but when i called the route or compile anything but /posts/ it was failing. I could call it posts but it would still output to the journal folder. But I was having weirdness. I was expecting whatever folder tree i build that would be what nanoc would output

15:33 <ddfreyne> timgauthier__: By default nanoc generates index.html files in directories, which leads to nice URLs (e.g. http://example.com/about/ instead of http://example.com/about.html)

15:34 <ddfreyne> timgauthier__: I'm at work and don't have that much time, but I am available later on

15:34 <ddfreyne> timgauthier__: Feel free to share the structure of your `content/` dir and the contents of the Rules file though. That could be helpful

15:34 <timgauthier__> i have a github for it

15:35 <ddfreyne> That is cool to

15:35 <ddfreyne> o

15:35 <timgauthier__> https://github.com/timgauthier/Nanoc-Tutorial

15:35 <ddfreyne> Alright, have to go for a bit. Will be around later

15:35 <timgauthier__> i dont think i will be on, as its in the evening here in europe, have fun though!

15:35 <ddfreyne> I am in Berlin, also Europe :)

15:35 <ddfreyne> AFK

15:36 <timgauthier__> Zwichau

17:57 <timgauthier> bloop

17:57 <timgauthier> ok, where did i write that post

18:05 <guardian> ddfreyne: any opinion on #413?

18:10 <timgauthier> why can’t route '/posts/*' do be route ‘/journal/*’ do?

18:10 <timgauthier> i missed some backticks and formatting in that.. bleh

18:21 <timgauthier> with an @item[] how can you do a check to see if it exsists? like if @item[:title]

18:35 <timgauthier> trying to install the nanoc-guard gem, having an error on bundle install http://pastie.org/9071045

19:16 <timgauthier> turns out it was that nasty bug with Clang again

19:37 <ddfreyne> timgauthier: If you have content/journal/ instead of content/posts/, you can use route '/journal/*/' instead of route '/posts/*/'

19:37 <ddfreyne> Those patterns correspond with the structure in the content/ directory

19:37 <timgauthier> does that following / make a difference?

19:37 <ddfreyne> timgauthier: @item[:title].nil? will return true if it is nil

19:38 <timgauthier> is there a logical opposite to that?

19:38 <ddfreyne> timgauthier: '/posts/*' would also match the identifier /posts/ itself, which is probably not what you want

19:38 <ddfreyne> timgauthier: @item[:title] will be true-y if it is not nil and not false

19:38 <ddfreyne> if @item[:title] ; ... ; end

19:38 <timgauthier> ok that makes sense

19:39 <ddfreyne> That clang error is weird.

19:39 <ddfreyne> I actually had something like that with clang before, now that I think of it... although that was with Go + OpenGL, heh

19:40 <ddfreyne> guardian: I'm a bit pressed for time, but if you can write a PR for #414 that would be really cool

19:40 <ddfreyne> (Rather, one that has parent_config_file)

19:42 <timgauthier> the clang error is due to OSX updating the xcode tools, and clang/ruby/rest of the world not being there yet

19:46 <timgauthier> how do you pronounce nanoc ? :P

19:46 <ddfreyne> nah-nock

19:47 <timgauthier> ok coo :P haha i’ve been saying it nah-nöck

20:02 <timgauthier> pretty late time to finish work :P

20:02 <timgauthier> what is the closest equivolent to site.variables like in jekyll?

20:03 <ddfreyne> I don't know what site.variables is.

20:03 <ddfreyne> You can add stuff to nanoc.yaml though, and later access it using @config[…]

20:44 <timgauthier> thanks that might be it

20:56 <ddfreyne> GitHub is acting up :(

21:06 <timgauthier> how so?

21:12 <ddfreyne> Seems to be OK now.

21:12 <ddfreyne> Anyway, sleep, night!

22:48 <timgauthier> how do you assign something to the nanoc.yaml so that i can use it later with @config[]?

22:51 <timgauthier_> asd

22:51 <timgauthier> sorry

22:58 <timgauthier> oh... that was way easier then i thought, never mind the adding a "variable" to the yaml thing, figured that out!

23:13 <timgauthier> with posts.compiled_content is there a way to excerpt and truncate?