From: Ingo Schwarze <schwarze@usta.de>
To: discuss@mdocml.bsd.lv
Subject: Re: EXIT STATUS for section 6
Date: Sat, 4 Sep 2010 00:42:08 +0200 [thread overview]
Message-ID: <20100903224208.GA5602@iris.usta.de> (raw)
In-Reply-To: <20100903192831.GB18815@bramka.kerhand.co.uk>
Hi Jason, hi Thomas,
Jason McIntyre wrote on Fri, Sep 03, 2010 at 08:28:07PM +0100:
> On Fri, Sep 03, 2010 at 06:29:05PM +0200, Thomas Klausner wrote:
> > On Fri, Sep 03, 2010 at 01:57:19PM +0100, Jason McIntyre wrote:
>>> the templates say EXIT STATUS is for sections 1 and 8. the descriptions
>>> of EXIT STATUS say it is for sections 1, 6, and 8. which is it?
>> Section 6 are games, so they could have an EXIT STATUS.
> could have, yeah. but don't.
For some cases, that's a documentation bug.
Take fortune(6) -m. The EXIT STATUS tells whether there were matches,
which ought to be documented.
Or try /usr/games/banner -w xxx BSD ; echo $?
>>> openbsd has no exit status info in any of its section 6 pages. ok?
>> Well, I thought you're only introducing EXIT STATUS in the OpenBSD man
>> pages? :)
> yeah. but i downcased EXIT STATUS - i meant none of the section 6pages
> have any info about what they return.
Some should.
NB: I don't blame you that they don't. But it's a task to read the
program sources and find out whether each one should.
>> Anyway, i don't see any EXIT STATUS in man6/* on NetBSD either.
>>
>> I think we should allow it for section 6 as well, but I don't care
>> much either way.
> right, so which way do we fall. section 6 ok or not? i don't care.
I'm clearly with Thomas here. EXIT STATUS in section 6 is needed.
Yours,
Ingo
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2010-09-03 22:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sfid-H20100903-145809-+038.18-1@spamfilter.osbf.lua>
2010-09-03 12:57 ` Jason McIntyre
2010-09-03 16:29 ` Thomas Klausner
2010-09-03 19:28 ` Jason McIntyre
2010-09-03 22:42 ` Ingo Schwarze [this message]
2010-09-04 6:52 ` Jason McIntyre
2010-09-04 17:22 ` Kristaps Dzonsons
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=20100903224208.GA5602@iris.usta.de \
--to=schwarze@usta.de \
--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).