discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: "Ulrich Spörlein" <uqs@spoerlein.net>
To: discuss@mdocml.bsd.lv
Cc: Thomas Klausner <wiz@NetBSD.org>
Subject: Re: mdoc.7: tweak skeleton file
Date: Sun, 29 Aug 2010 20:06:13 +0200	[thread overview]
Message-ID: <20100829180613.GI3523@acme.spoerlein.net> (raw)
In-Reply-To: <4C7A983C.3000900@bsd.lv>

On Sun, 29.08.2010 at 19:26:20 +0200, Kristaps Džonsons wrote:
> > well, there is nothing to say we have to move it at all. it can stay in the
> > place it always was.
> > 
> > however for openbsd, the choice is not so important - we currently don;t
> > have EXIT STATUS, so as far as workload goes, it's irrelevant where we add
> > it.
> > 
> > i personally think it is best placed immediately after DESCRIPTION,
> > where it always was. please let us not just think about what posix does
> > when making this decision. i'd welcome feedback from any freebsd people
> > at this point - maybe there was a good reason for the change.
> > 
> > anyway, my diff below should make us match (almost) for mdoclint. note
> > that you need to make "IMPLEMENTATION NOTES" defined for netbsd only,
> > and "EXIT STATUS" now not os-specific.
> > 
> > let me know what you want to do about section placement.
> 
> Note that Ruslan, whom I understand does a lot of FreeBSD manual stuff, 
> isn't part of this list.  So if you want to involve him, you'll have to 
> CC him...

I can't speak with any authority on this topic, as it far predates my
mdoc involvement.

But this is the blessed ordering for the FreeBSD manpages, where EXIT
STATUS was taken (and ordered) from the POSIX manpages.

sections = [
    '00',
    'NAME',
    'LIBRARY',
    'SYNOPSIS',
    'DESCRIPTION',
    'IMPLEMENTATION NOTES',
    'RETURN VALUES',
    'ENVIRONMENT',
    'FILES',
    'EXIT STATUS',
    'EXAMPLES',
    'DIAGNOSTICS',
    'COMPATIBILITY',
    'ERRORS',
    'SEE ALSO',
    'STANDARDS',
    'HISTORY',
    'AUTHORS',
    'CAVEATS',
    'BUGS',
    'SECURITY CONSIDERATIONS',
]
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2010-08-29 18:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-26 18:24 Jason McIntyre
2010-08-28 21:12 ` Kristaps Dzonsons
2010-08-28 22:01   ` Jason McIntyre
2010-08-28 22:08     ` Kristaps Dzonsons
2010-08-28 22:18       ` Jason McIntyre
2010-08-28 22:38       ` Jason McIntyre
2010-08-28 23:14         ` Kristaps Dzonsons
2010-08-29  9:10           ` Jason McIntyre
2010-08-29 10:50             ` Thomas Klausner
2010-08-29 11:33               ` Jason McIntyre
2010-08-29 12:09                 ` Thomas Klausner
2010-08-29 16:17                   ` Jason McIntyre
2010-08-29 17:26                     ` Kristaps Dzonsons
2010-08-29 18:06                       ` Ulrich Spörlein [this message]
2010-08-29 18:28                         ` Jason McIntyre
2010-08-29 20:57                           ` Thomas Klausner
2010-08-30  6:43                             ` Jason McIntyre
2010-08-30  9:01                               ` Thomas Klausner
2010-08-30 12:16                                 ` Jason McIntyre
2010-08-30 12:21                                   ` Thomas Klausner
2010-08-30 12:29                                     ` Kristaps Dzonsons
2010-08-31 17:54                                   ` Jason McIntyre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100829180613.GI3523@acme.spoerlein.net \
    --to=uqs@spoerlein.net \
    --cc=discuss@mdocml.bsd.lv \
    --cc=wiz@NetBSD.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).