06:59 <guardian> ddfreyne: https://jira.codehaus.org/browse/JRUBY-1277 the way I understand the comments on this issue, I understand something's been fixed on JRuby side

06:59 <guardian> ddfreyne: unfortunately the issue doesn't link to a commit

08:47 <ddfreyne> guardian: It is not fixed in nanoc

08:47 <ddfreyne> USR1 is reserved for the JVM and nanoc trying to take control of it fails

08:48 <ddfreyne> That issue is from 5 years ago.

08:48 <ddfreyne> Sorry, 7

08:49 <ddfreyne> guardian: So disabling it on nanoc+JRuby seems like a decent way forward

09:07 <prxq_> guardian: thanks

10:13 <cDlm> what was usr1 used for ?

10:40 <guardian> ddfreyne: yeah I started with the issue in the nanoc PR queue then tried to understand the situation until I found that bug report that pretends it's fixed in JRuby

11:33 <guardian> ddfreyne: so sending USR1 in the middle of a nanoc compile dumps a stack trace?

11:35 <guardian> ddfreyne: or is it intended to send USR1 from within a helper or filter and get the outerloop dump a stack trace?

13:43 <ddfreyne> guardian: USR1 is used to dump the stack trace. It's useful to find out what nanoc is doing exactly

13:43 <ddfreyne> (It's a nanoc thing)

13:44 <ddfreyne> It's purely a debugging thing. It can be disabled easily

13:58 <guardian> but who sends USR1

13:58 <guardian> and when?

13:58 <guardian> is it you launch nanoc compile and from another term you kill -USR1 nanoc?

14:14 <ddfreyne> guardian: yup

14:26 <guardian> uh!

14:26 <guardian> is it really useful?

14:26 <guardian> like, I launch nanoc compile, at the time kill -USR1 nanoc is fired, I have no idea which stack trace gonna be dumped

14:28 <ddfreyne> guardian: It's useful in a situation where nanoc apparently hangs

14:28 <ddfreyne> If you send SIGUSR1, you'll know where it hangs

14:29 <guardian> ok

15:45 <jugglinmike> Does anyone here use nanoc inside a VM? Possibly with Vagrant? I'm just setting this up, and seeing a lot of needless re-compilation happening. I'm wondering if this has something to do with the host/guest shared folder syncing

15:45 <guardian> interesting

15:45 <guardian> can you please ping me once you figured that out?

15:56 <jugglinmike> guardian: I'll let you know what I come up with

16:28 <jugglinmike> guardian: User error

16:29 <jugglinmike> I still have an `output/` directory on my host machine. Every time I changed something in `content/`, the `output/` on the host was ALSO being rsync'd to the guest, and nanoc (running on the guest) correctly identified that those output files needed to be re-compiled

16:30 <jugglinmike> adding "output/" to the `rsync__exclude` list fixed the problem

16:30 <guardian> ok

18:29 <prxq> is there a way to do "nested" layouts? I have parts of pages that appear in more than one other page...

18:30 <bobthecow> yes.

18:31 <bobthecow> you can use the rendering helper: http://nanoc.ws/docs/api/Nanoc/Helpers/Rendering.html

18:32 <bobthecow> or, if your layouts are like matryoshka dolls, you can use multiple `layout` calls in your rules file.

18:33 <bobthecow> prxq: ^

18:35 <prxq> thanks

20:38 <ddfreyne> If you think I'm not doing a lot of nanoc work lately, here's why:

20:38 <ddfreyne> http://ddfreyne.github.io/spaaace/

20:38 <ddfreyne> up/left/right/down/L

20:38 <ddfreyne> are the controls

20:38 <ddfreyne> Totally unfinished. Don't expect anythign fancy.

21:37 <bobthecow> ddfreyne: all i'm getting from this is that space is big and empty and boring if you don't know where you're going ;)

21:39 <bobthecow> are there other places to go besides ceres, pallas and juno?