From: Jason McIntyre <jmc@kerhand.co.uk>
To: Ruslan Ermilov <ru@FreeBSD.org>
Cc: discuss@mdocml.bsd.lv
Subject: Re: mdoc EXIT STATUS (Was: pending open issues)
Date: Wed, 28 Jul 2010 14:38:18 +0100 [thread overview]
Message-ID: <20100728133842.GB31150@bramka.kerhand.co.uk> (raw)
In-Reply-To: <20100728123317.GA43609@edoofus.dev.vega.ru>
On Wed, Jul 28, 2010 at 04:33:17PM +0400, Ruslan Ermilov wrote:
> >
> > what exactly is the purpose of having two sections? how do you separate
> > application diagnostics from their return codes?
>
> Well, exit statuses and diagnostic messages aren't necessarily related.
> Like I said, the main reason for introducing the EXIT STATUS section
> was to follow POSIX. DIAGNOSTICS was left untouched for documenting
> diagnostic messages. POSIX uses STDERR for this purpose, let me quote
> the relevant text:
>
> : The STDERR section describes the standard error output of
> : the utility. Only those messages that are purposely sent by
> : the utility are described.
[snip]
thanks, that's clarified some questions i had. i'll wait and see what
netbsd people have to say too. i think though, that we probably won;t
reinstate EXIT STATUS - it feels too silly having a section for what
essentially amounts to a single sentence.
>
> > i'm struggling to find a page (sections 1, 6, or 8) where DIAGNOSTICS
> > makes sense. i cannot even find any posix pages with it. or are you just
> > using DIAGNOSTICS for section 4?
>
> See http://www.freebsd.org/cgi/man.cgi?route for one such
> example.
>
yes, that seems to be one of the few 1/6/8 pages with a reasonable
DIAGNOSTICS section.
jmc
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2010-07-28 13:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C4E0F7B.4030009@bsd.lv>
[not found] ` <20100727071224.GB7946@bramka.kerhand.co.uk>
2010-07-27 8:31 ` pending open issues Kristaps Dzonsons
2010-07-27 9:00 ` Sascha Wildner
2010-07-27 9:20 ` Jason McIntyre
2010-07-27 9:32 ` Kristaps Dzonsons
2010-07-27 9:41 ` Jason McIntyre
2010-07-27 10:03 ` Kristaps Dzonsons
2010-07-27 10:18 ` Jason McIntyre
2010-07-27 11:21 ` mdoc EXIT STATUS (Was: pending open issues) Kristaps Dzonsons
[not found] ` <20100727131709.GA16499@edoofus.dev.vega.ru>
2010-07-27 13:54 ` Kristaps Dzonsons
2010-07-27 14:15 ` Jason McIntyre
[not found] ` <20100728123317.GA43609@edoofus.dev.vega.ru>
2010-07-28 13:38 ` Jason McIntyre [this message]
2010-08-03 21:28 ` Ingo Schwarze
2010-08-03 21:34 ` Joerg Sonnenberger
2010-08-06 15:48 ` Kristaps Dzonsons
2010-08-06 16:17 ` Ingo Schwarze
2010-08-06 16:36 ` Kristaps Dzonsons
2010-08-04 6:57 ` 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=20100728133842.GB31150@bramka.kerhand.co.uk \
--to=jmc@kerhand.co.uk \
--cc=discuss@mdocml.bsd.lv \
--cc=ru@FreeBSD.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).