<ddfreyne>
Now comes with notification support (growl, leopard user notifications, …) and compilation feedback
<musicmatze>
What does this guard-nanoc do?
<ddfreyne>
musicmatze: It is quite similar to `nanoc watch`
<musicmatze>
ah okay.
<ddfreyne>
Except that guard does a lot more for you, so the implementation of guard-nanoc is a lot simpler than the watch command
<ddfreyne>
(And a lot more reliable, too)
remko_ has joined #nanoc
<remko_>
hi. Too lazy to check the source, but can you return a list from 'route' commands?
<remko_>
to have aliases
<ddfreyne>
remko_: You can’t. Wouldn’t it be better to set up redirects anyway?
<remko_>
i don't really want a redirect, i'd like different URLs
<ddfreyne>
But with exactly the same content?
<remko_>
yeah. I know, bit of a corner case. Still, what if you don't have control over your web server? (e.g. basic hosting providers)
<ddfreyne>
remko_: I’d recommend a META rediret
<ddfreyne>
remko_: I’d recommend a META redirect
<remko_>
ok
<musicmatze>
ddfreyne: Thank you for your comment on my latest patch of nanoc.
<musicmatze>
The problem is: I did a rebase to the latest release-3.6.x commit and some more (small) syntatic suggar-changes. Can I resubmit the whole stuff and close the actual pullrequest?
<musicmatze>
ah wait, the branch on my github repo is still alive...
pavelkunc has quit [Quit: Leaving.]
<ddfreyne>
musicmatze: Can you reuse the same branch?
<musicmatze>
yes, I can.
<musicmatze>
Done. Pull request is updated.
<ddfreyne>
musicmatze: Alright, cool. I’ll wait for the Travis results and merge afterwards
<musicmatze>
Thanks.
<guardian>
o/
<guardian>
ddfreyne or bobthecow what's your position on: is it a good or bad idea to extract created_at / updated_at item metadata from git? I can't make my mind about it
<ddfreyne>
guardian: I would say no. I call it published_on (a Date) and I don’t have an updated_at
<guardian>
yeah I call it published_on and updated_on
<guardian>
but many sites (following mgutz template I would say) use created_at and updated_at
<ddfreyne>
guardian: You could get updated_at from git, I guess
<guardian>
commit a typo fix, do you want the item to pop up in the feed?
<guardian>
not really I think
<ddfreyne>
Agree
<ddfreyne>
d
<musicmatze>
Maybe I bring in an idea: I used scripts to write new blogging articles for jekyll: create new item, open it with vim, check it with aspell and then commit it with "post added".
<musicmatze>
Maybe you could parse the commit messages and search for "post added" and take this as published_on or so.
<guardian>
yep
<guardian>
or just leave git out of the way
<musicmatze>
that's another option, right! :D
<guardian>
have a new article nanoc command that populates published_on
<guardian>
and have a touch article that populates updated_on
<guardian>
in case I really don't want to do that manually
<guardian>
I realize often I go "would so great if…" then soon after "fuck that shit you're not writing a CMS"
remko_ has left #nanoc [#nanoc]
alerante has joined #nanoc
alerante has quit [Remote host closed the connection]