From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp-2.sys.kth.se (smtp-2.sys.kth.se [130.237.32.160]) by krisdoz.my.domain (8.14.3/8.14.3) with ESMTP id o4BGLdXS015147 for ; Tue, 11 May 2010 10:21:40 -0600 (MDT) Received: from localhost (localhost [127.0.0.1]) by smtp-2.sys.kth.se (Postfix) with ESMTP id D4C8D14DD35 for ; Tue, 11 May 2010 22:09:52 +0200 (CEST) X-Virus-Scanned: by amavisd-new at kth.se Received: from smtp-2.sys.kth.se ([127.0.0.1]) by localhost (smtp-2.sys.kth.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id pWDYbwuEjBgo for ; Tue, 11 May 2010 22:09:51 +0200 (CEST) X-KTH-Auth: kristaps [85.8.60.171] X-KTH-mail-from: kristaps@bsd.lv X-KTH-rcpt-to: discuss@mdocml.bsd.lv Received: from lappy.bsd.lv (h85-8-60-171.dynamic.se.alltele.net [85.8.60.171]) by smtp-2.sys.kth.se (Postfix) with ESMTP id 32D3A14DCD1 for ; Tue, 11 May 2010 22:09:50 +0200 (CEST) Message-ID: <4BE9B98D.3060706@bsd.lv> Date: Tue, 11 May 2010 22:09:49 +0200 From: Kristaps Dzonsons User-Agent: Thunderbird 2.0.0.16 (X11/20080812) X-Mailinglist: mdocml-discuss Reply-To: discuss@mdocml.bsd.lv MIME-Version: 1.0 To: "discuss@mdocml.bsd.lv" Subject: Re: mdoc section ordering References: <20100511115233.GV88504@acme.spoerlein.net> <20100511134542.GA24992@bramka.kerhand.co.uk> <20100511145711.GW88504@acme.spoerlein.net> <20100511154317.GB24992@bramka.kerhand.co.uk> <20100511162352.GY88504@acme.spoerlein.net> In-Reply-To: <20100511162352.GY88504@acme.spoerlein.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit > I'm fine with that, only then mandoc should stop "enforcing" this > ordering. It's perfectly fine with me! > > Kristaps, what to you think? Seems the consensus is to roll with the FreeBSD version, which is fine by me. The sections were originally unioned over all mdoc.template and man.template files I could find. I didn't sweat the order. End result: .Sh NAME .Sh LIBRARY .Sh SYNOPSIS .Sh DESCRIPTION .Sh IMPLEMENTATION NOTES <-- this one seems wankiest to me .Sh RETURN VALUES .Sh ENVIRONMENT .Sh FILES .Sh EXIT STATUS .Sh EXAMPLES .Sh DIAGNOSTICS .Sh COMPATIBILITY .Sh ERRORS .Sh SEE ALSO .Sh STANDARDS .Sh HISTORY .Sh AUTHORS .Sh CAVEATS .Sh BUGS .Sh SECURITY CONSIDERATIONS <-- shouldn't this be CAVEATS? Jason, in my opinion, COMPATIBILITY and STANDARDS shouldn't be merged in all cases. Take mdocml's man.7 and mdoc.7, for example: the COMPATIBILITY section is used to enumerate the differences between troffs and mandoc. Since -man, -mdoc, etc. aren't standards, where else would this go? Anyway, if everybody ok's this order, I'll commit it and add the requisite bits to the docs. Ulrich, you said you know of a handful of mis-ordered NetBSD pages. Can you post those to Joerg? He'll probably want to know about them (will your python script auto-gen a patch for him?). Thanks, Kristaps -- To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv