[11:28] <Keybuk> sadmac2: I was thinking "We do what we must because we can" :-)
[11:29] <Keybuk> mbiebl: yeah, the script was literally just a hack - if you've got a better version please do open an LP bug and I'll replace it
[11:29] <Keybuk> mbiebl: obviously the LP bug should be against the Ubuntu package ;)
[11:30] <ion> keybuk: So...? :-)
[11:30] <Keybuk> sadmac2: I haven't received the state transfer patch from you, I don't think - let me check
[11:30] <Keybuk> ion: please do fix any errors you see in the manpages, or even rewrite bits if you like ;)  I literally just wrote them all in a morning after getting carried away editing RH's events(5) page
[11:31] <Keybuk> ion: they're just wrapped in emacs at 80 columns I think - but obviously the wrapping goes awry when you edit the pages afterwards
[11:31] <ion> Well, i’d use vim’s gq command to rewrap after any changes.
[11:32] <Keybuk> that gets manpages wrong though, right?
[11:32] <Keybuk> it tries to move the .B bits back onto the same line
[11:32] <ion> some text, blah blah (cursor here)
[11:33] <ion> more text, foobar
[11:33] <ion> .B baz
[11:34] <ion> 2gqgq rewraps the two lines, not touching the .B line. When there are so many lines it’s not easy to count them with a single skim, V switches to visual mode (”paint lines” mode), j extends the selected area downwards and gq finally rewraps it.
[11:34]  * Keybuk remembers why he uses emacs ;)
[11:34] <ion> 2gqq even
[11:35] <ion> Emacs has built-in functionality to rewrap man pages properly?
[11:35] <Keybuk> C-A-\
[11:35] <ion> Neat
[11:35] <Keybuk> well, rewrap anything really
[11:35] <Keybuk> I'd still rather use anjuta though
[11:35] <ion> But it didn’t seem to wrap the Upstart manpages consistently.
[11:37] <Keybuk> that's because I didn't use it :)
[11:37] <Keybuk> I just typed stuff
[11:38] <Keybuk> it wrapped as I went
[11:38] <Keybuk> then I went back and editing things I typed
[11:38] <Keybuk> but I didn't rewrap after
[11:38] <Keybuk> I probably sometimes pressed enter manually to wrap too ;)
[11:42] <ion> vim seems to support letting an external program or a vimscript function handle gq for certain filetypes. I wonder if one of the text formatters available from apt support manpages?
[11:42] <Keybuk> no idea
[11:48] <Keybuk> sadmac2: ah, I do - you added an "also affects 0.3" which sent it to the other mailbox
[11:48]  * Keybuk fixes his mailer confi
[11:55] <ion> Ha! One can tell par 'P=.' and it “protects” lines starting with a dot. I’ll see if par handles manpages nicely otherwise.
[12:07] <Keybuk> ion: the trick though is keeping them formatted ;)
[12:54] <Keybuk> mbiebl: I fixed the test_control failure ;)
[12:54] <Keybuk> it was a brain failure
[14:41] <Keybuk> now I have a strange test case failure
[14:41] <Keybuk> that only seems to affect my laptop
[14:41]  * Keybuk wonders whether Upstart's test suite has uncovered a bug in the new fanotify() kernel stuff
[16:51] <Keybuk> well, the kernel update solves the other inotify bug I'd noticed
[16:51] <Keybuk> but not this one
[23:00] <Keybuk> ok iz confirmed
[23:00] <Keybuk> the test_conf failure is a kernel bug ;)
[23:23] <ion> Does 0.6 already use the magic to follow forks?
[23:31] <Keybuk> no, it just uses ptrace
[23:31] <ion> Ok
[23:33] <Keybuk> though since I binned the session leader crap, that actually appears to work
[23:34] <Keybuk> well
[23:34] <Keybuk> kinda
[23:36] <ion> Have you already started working on the mount daemon? I wonder if i’d manage to contribute anything some day... An often-updated repository with a TODO list would be nice. :-)
[23:36] <Keybuk> no, not yet
[23:36] <Keybuk> I'll try and do that ;)
[23:38] <Keybuk> hmm, processes get kinda stuck in ptrace