ddfreyne changed the topic of #nanoc to: 3.6.2 (mar 23th) | web http://nanoc.ws/ | repo http://bit.ly/XE6e3G | issues http://bit.ly/VfXaSV | forum http://ho.io/n-discuss | irclog http://irclog.whitequark.org/nanoc
louquillio has joined #nanoc
LBo has quit [Ping timeout: 240 seconds]
LBo has joined #nanoc
alerante has joined #nanoc
<bobthecow> guardian: yes.
<bobthecow> very yes.
<bobthecow> ddfreyne: guard-nanoc works great for me, still does that max recursion depth for my buddy.
<bobthecow> but it's awesome for me :)
<ddfreyne> bobthecow: The max recursion depth thing is really weird :/
<ddfreyne> I would love to be able to reproduce it, too
<ddfreyne> Anyway, it’s past 4 AM here, so I should get sleep :D
<bobthecow> heh
<bobthecow> any progress on taking over guard-nanoc gem?
<ddfreyne> bobthecow: I haven’t received a reply from Yann Lugrin yet :(
<ddfreyne> Sleep time now, gnight!
whk has left #nanoc [#nanoc]
jadd_ has joined #nanoc
jadd_ has quit [Quit: Leaving...]
alerante has quit [Remote host closed the connection]
jadd_ has joined #nanoc
jadd_ has quit [Quit: Leaving...]
<musicmatze> Hey, guys. Do you want to laught? Here is my implementation of a blockquote for nanoc: http://sprunge.us/SMcc and here is a jekyll-plugin which does the same: http://sprunge.us/PWeV
<musicmatze> do you see the difference? 33 lines (really readable code) vs. 82 lines (unreadable code)! :D
<guardian> bobthecow: but it looks ugly unstyled :/ well floated thumbnails do
<ddfreyne> musicmatze: NIce :)
<musicmatze> :D
<ddfreyne> musicmatze: I’m no fan of Liquid
<musicmatze> Me too!
<ddfreyne> nanoc 1.x and 2.x had Liquid support but I dropped thaht
<ddfreyne> -h
<musicmatze> Thank you for this! :D
<ddfreyne> It was really hard to maintain too
<ddfreyne> I hope Yann replies soon so guard-nanoc can become official!
<musicmatze> Ouh, you deleted very much code since my last fetch.
<ddfreyne> musicmatze: In experimental-4.x? Yeah
<ddfreyne> create-item, create-layout, autocompile, watch, validate-* commands are all gone, for instance
pavelkunc has joined #nanoc
<musicmatze> why did you remove this stuff?
<musicmatze> lets say, why did you remove autocompile for example.
<musicmatze> ?*
<ddfreyne> create-item and create-layout can easily be done manually
pavelkunc has quit [Client Quit]
<ddfreyne> autocompile and watch are replaced by guard-nanoc
<musicmatze> okay, so why create-item?
<ddfreyne> validate-* are replaced by the check command (they were actually very thin wrappers for check already )
<ddfreyne> musicmatze: I never use create-item; I just create the relevant file in content/ manually
<musicmatze> okay, so you did not remove them because they need a rewrite. They are already rewritten, as I understand.
<ddfreyne> No, I removed them because they’re not very useful
<musicmatze> so I do.
<musicmatze> okay. I think this will speed up nanoc a little bit, too. Right? Because the ruby interpreter doesn't have to care about the code :-)
<ddfreyne> musicmatze: Probably not noticeably though :)
<ddfreyne> Hmm, need your opinion: mention GitHub issue numbers in the release notes? That could be pretty useful to keep track of things.
<ddfreyne> bobthecow: ↑
<ddfreyne> There’s multiple issues for each change usually though (a reported issue and a pull request to fix it)
<guardian> create-item removed?
<guardian> where? master?
<ddfreyne> guardian: experimental-4.x
<guardian> ok
<guardian> i'm hesitating doing custom create commands
<guardian> but I think I repeat myself: sometimes it feels handy, sometimes it feels like writing a cms on top of nanoc
<guardian> and in that case I often end up thinking: "as if we had gcc create-file" command :)
<ddfreyne> guardian: Yep, that’s one of the reasons why I’m getting rid of create-item and create-layout
<ddfreyne> woot, I just implemented symlink support for content/
<guardian> did you have a look at that issue with routing and passthrough?
<ddfreyne> guardian: I did. I’m going to look at it again today, I promise!
<guardian> oh that's ok it's just to know whether I need to remember to patch 3.6.3 when released :)
<ddfreyne> Looks good already though
<ddfreyne> Who wants to review this? ↑ :)
<ddfreyne> guardian: Can you write a test case for your pull request?
<ddfreyne> I can do that too if you would rather have me do it
<guardian> hmm
<guardian> where to start?
louquillio_ has quit [Remote host closed the connection]
<musicmatze> ddfreyne: I updated some stuff in my site. Please pull these changes. If you want to compile, you may checkout the plugins branch.
* musicmatze is away now. lunch.
<ddfreyne> musicmatze: Okay I will, take care
<ddfreyne> guardian: Hmm, let me write it. It’s probably easier that way (not an easy test to write)
<ddfreyne> Yikes, decent symlink handling is pretty hard
Skyr has quit [Ping timeout: 245 seconds]
Skyr has joined #nanoc
<ddfreyne> Whew, symlinks in content/ should now work!
<ddfreyne> Nah, still not ok
<ddfreyne> Damn symlinks!
<ddfreyne> afk
Skyr has quit [Ping timeout: 245 seconds]
Skyr has joined #nanoc
Skyr has quit [Ping timeout: 256 seconds]
Skyr has joined #nanoc
Skyr has quit [Ping timeout: 264 seconds]
Skyr has joined #nanoc
<musicmatze> Can anyone tell me how to generate a rss feed with nanoc?
<musicmatze> Skyr: Maybe you?
<ddfreyne> musicmatze: You can use the atom_feed helper
<musicmatze> thank you. Do I have to create a new Item for this?
<musicmatze> Say, @items << Item.new(atom_feed(some_articles), ...) or so?
Skyr has quit [Read error: Operation timed out]
<ddfreyne> musicmatze: I’d just create a new item in content/
<ddfreyne> musicmatze: In general, it’s better to prefer creating stuff in content/ rather than in the preprocessor, because the preprocessor always runs
Skyr has joined #nanoc
Skyr has quit [Ping timeout: 260 seconds]
Skyr has joined #nanoc
<musicmatze> The problem is, I want to create a feed per blog category. I have to do this in the preprocessor, I think!
<ddfreyne> musicmatze: Ahh, probably yes… you can do it using the @items << that you suggested
<musicmatze> Okay, thank you.
<musicmatze> What did you mean with "the preprocessor always runs" ?
<musicmatze> Did you mean it runs always on each "nanoc compile" call or did you mean it runs all the time while nanoc is compiling?
<ddfreyne> musicmatze: It runs on every compile call, entirely
<ddfreyne> musicmatze: That means that if you do filtering etc, it is always done, which is inefficient
alerante has joined #nanoc
<musicmatze> Yes, that's bad, of course. But I do not see another way to do this.
<ddfreyne> musicmatze: I took a look at your site and I think you already do some filtering in the preprocessor, no?
<ddfreyne> Haven’t had a chance to compile it yet, and busy with something else now :(
<musicmatze> yes. But more generating content.
<musicmatze> Generating tag pages and category pages
<musicmatze> and archive pages and so on ...
<ddfreyne> Yeah… I think that can be more efficient, but I’ll see and let you know!
<musicmatze> Thanks.
Skyr has quit [Ping timeout: 248 seconds]
Skyr has joined #nanoc
alerante has quit [Remote host closed the connection]
alerante has joined #nanoc
matjas has quit [Ping timeout: 246 seconds]
matjas has joined #nanoc
<ddfreyne> Looks like I’ll need to merge master to experimental-4.x very regularly!
<ddfreyne> Never had this many merge conflicts ;D
bitslip_ has joined #nanoc
bitslip has quit [Read error: Connection reset by peer]
Segismond_ has joined #nanoc
Segismond has quit [Ping timeout: 252 seconds]
louquillio has quit [Remote host closed the connection]
pavelkunc has joined #nanoc
louquillio has joined #nanoc
louquillio has quit [Remote host closed the connection]