From: "Ulrich Spörlein" <uqs@spoerlein.net>
To: discuss@mdocml.bsd.lv
Subject: Re: mdoc section ordering
Date: Tue, 11 May 2010 18:23:52 +0200 [thread overview]
Message-ID: <20100511162352.GY88504@acme.spoerlein.net> (raw)
In-Reply-To: <20100511154317.GB24992@bramka.kerhand.co.uk>
On Tue, 11.05.2010 at 16:42:53 +0059, Jason McIntyre wrote:
> On Tue, May 11, 2010 at 04:57:11PM +0200, Ulrich Sp??rlein wrote:
> >
> > To clarify, none of these sections shall become mandatory. It's just the
> > ordering that mandoc -Tlint would complain about iff such a section
> > exist.
> >
>
> ah, sorry, i misunderstood then. so yeah, it makes no difference to us.
>
> > I did a quick grep over the OpenBSD tree and it seems that EXIT STATUS
> > isn't really used at all, and where it is used the ordering is not
> > impacted as there are no RETURN VALUES, ENVIRONMENT or FILES sections
> > nearby.
> >
> > NetBSD however has a couple of pages where FILES or ENVIRONMENT come
> > after EXIT STATUS and that means one of NetBSD or FreeBSD would need to
> > change a couple of pages.
> >
>
> as far as i know, EXIT STATUS is not even a standard section header. for
> example, the groff_mdoc.7 page that comes with the latest groff does not
> list it. so maybe there is no issue, and you shouldn;t worry about where
> it's put?
I'm fine with that, only then mandoc should stop "enforcing" this
ordering. It's perfectly fine with me!
Kristaps, what to you think?
Regards,
Uli
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2010-05-11 12:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 11:52 Ulrich Spörlein
2010-05-11 13:45 ` Jason McIntyre
2010-05-11 14:57 ` Ulrich Spörlein
2010-05-11 15:43 ` Jason McIntyre
2010-05-11 16:23 ` Ulrich Spörlein [this message]
2010-05-11 20:09 ` Kristaps Dzonsons
2010-05-11 20:27 ` Ulrich Spörlein
2010-05-11 20:59 ` Jason McIntyre
2010-05-12 12:50 ` Kristaps Dzonsons
2010-05-13 22:23 ` Thomas Klausner
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=20100511162352.GY88504@acme.spoerlein.net \
--to=uqs@spoerlein.net \
--cc=discuss@mdocml.bsd.lv \
/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).