07:13 <ddfreyne> skroon_: yeah you can pass your own list of articles to other functions

07:13 <ddfreyne> articles/sorted_articles just provide sensible defaults

09:23 <guardian> o/

09:24 <guardian> ddfreyne: how can I hack a way to compile a single item?

11:05 <musicmatze> ddfreyne: s/functions/methods/

11:05 <musicmatze> :-P

11:35 <musicmatze> Hi there. Version 0.0.4-0 of my static site compiler was released tonight! That means, I'm writing modules from now on. Just if you're interested...

11:49 <ddfreyne> guardian: You can't easily in nanoc 3.x but it will be easier in nanoc 4.x

11:49 <ddfreyne> musicmatze: Cool! where can I find it?

11:50 <guardian> does nanoc has an helper to go up a path?

11:50 <guardian> like /a/b/c/ —> go up —> /a/b/

11:52 <ddfreyne> guardian: a Nanoc::Item has a #parent

11:52 <ddfreyne> (the parent can be nil)

11:52 <ddfreyne> guardian: Also see the breadcrumbs helper

11:52 <guardian> I said path, not identifier

11:53 <ddfreyne> nope

11:53 <guardian> anyways, found another way

11:54 <guardian> I'm massing my robots.txt so that it disallows archive pages… I'm not happy with them appearing in google results when entering site:pempek.net

11:57 <musicmatze> ddfreyne: github.com/matthiasbeyer/thessc

11:58 <musicmatze> But as there are no modules yet, you cannot compile anything ! :-P

12:00 <musicmatze> By they way: Reading a file-tree in C is ugly! Really!

12:04 <ddfreyne> musicmatze: how so?

12:06 <musicmatze> -> man scandir

12:06 <ddfreyne> yeah it's not ideal :)

12:07 <musicmatze> Running filter functions which return numbers, but when you compile, the compiler tells you that returning a number is not correct or so, because it wants an enum... I finally figured it out how to do it yesterday night after ~2 hours dealing around with compiler warnings!

12:08 <musicmatze> Ideal would be : int getfilepaths(const char *root, char **pathes_dest, size_t *len_dest);

12:09 <musicmatze> maybe with 'int flags' for config (follow symlinks, bla bla)

12:15 <musicmatze> ddfreyne: Found an old tweet from you: "The diff between nanoc 3.x and nanoc 4.0 is over 300 screenfuls already. It sure is making progress!" - 1. Mai 2013! lol!

12:17 <_rgn> when's 4.0 gonna be out and will there be a document on how to migrate

12:21 <musicmatze> that's indeed a good question! :-P

12:30 <ddfreyne> nanoc 4.0 has no release date, but the idea is to improve it incrementally and keep it usable all the time

12:31 <ddfreyne> There will be a migration document, and I've been meanign to write that up... haven't gotten to it yet

12:31 <ddfreyne> (It will remain incomplete for some time)

12:31 <ddfreyne> It will be significantly easier to go from 3 to 4 than it was to go from 2 to 3.

19:32 <ddfreyne> !tell bobthecow Do you think output.diff is useful? I'm thinking of scratching that, and telling people to use git diff (with the output dir being a submodule or in a separate branch)

19:32 <number-six> ddfreyne: I'll pass that on when I see bobthecow here.