discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Kristaps Dzonsons <kristaps@bsd.lv>
To: "ru@freebsd.org" <ru@freebsd.org>
Cc: discuss@mdocml.bsd.lv
Subject: Re: mdoc EXIT STATUS (Was: pending open issues)
Date: Tue, 27 Jul 2010 15:54:55 +0200	[thread overview]
Message-ID: <4C4EE52F.9020601@bsd.lv> (raw)
In-Reply-To: <20100727131709.GA16499@edoofus.dev.vega.ru>

>> There's a discussion on mandoc's discuss@ list about the EXIT STATUS 
>> situation across the BSDs.  We're trying to unify the documentation in 
>> mandoc's mdoc.7 page (enclosed).
>>
>> Basically, everybody seems to have a different convention of where to 
>> put `Ex'.  Can you weigh in on FreeBSD's stance?
> 
> Traditionally BSD used DIAGNOSTICS for both exit statuses and diagnostic
> messages.  Then POSIX took BSD manpages to form their document base.
> They invented EXIT STATUS.  In 2000, I participated in mdoc(7) macro
> package rewrite in Groff, including massive updates of FreeBSD manpages.
> As part of this work, FreeBSD received permission from Austin Group to
> use POSIX texts in their manpages.  I've then "introduced" EXIT STATUS
> to FreeBSD manpages, in 2005, splitting the existing DIAGNOSTICS section
> into two: EXIT STATUS for documenting program's exit statuses, and
> DIAGNOSTICS for program/driver diagnostic messages.  The current
> manpage skeletons are there:
> 
> http://svn.freebsd.org/viewvc/base/head/share/misc/mdoc.template
> http://svn.freebsd.org/viewvc/base/head/share/examples/mdoc/
> 
> Note: We didn't modify the mdoc(7) manpage, it comes verbatim (without
> FreeBSD local changes) as found in the Groff distribution.  
> 
>> Jason McIntyre wrote:
>>> On Tue, Jul 27, 2010 at 12:03:21PM +0200, Kristaps Dzonsons wrote:
>>>> So, from what I gather
>>>>
>>>>  (1) Net uses EXIT STATUS
>>>>  (2) DragonFly/Free uses DIAGNOSTICS
>>>>  (3) Open uses DESCRIPTION
>>>>  (4) GNU/Linux uses chaos
>>>>
>>>> Is that correct?
>>> no. i can't speak for dragonfly, but netbsd and freebsd both use EXIT
>>> VALUES and DIAGNOSTICS. however i cannot find anywhere in their
>>> documentation that says EXIT STATUS is valid (mdoc.template perhaps
>>> being an exception, but that is not documentation).
>>>
>>> from what sacha said earlier, it sounds like dragonfly do this too.
>>>
>>> openbsd use DIAGNOSTICS, but not EXIT STATUS.
>>>
>>> i am deliberating whether it's worth reinstating EXIT STATUS, but i
>>> can;t get anyone authorative from these projects to say what "official
>>> policy" is. at least:
>>>
>>> 	net: wiz? joerg?
>>> 	free: i have no real contact with freebsd people. i don;t know
>>> 		who to ask.
>>> 	dragon: sacha, who is at least replying to this thread ;)
>>>
>>> it would be nice if between us we could agree on sth sane.

Ruslan, thanks!

So we have Free and DragonFly using EXIT STATUS (which is not documented
in mdoc.7 on either system).

From what I see of their manuals, NetBSD does the same, but let's wait
for an official word from wiz@ and/or joerg@.

Kristaps
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

  parent reply	other threads:[~2010-07-27 13:57 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 [this message]
2010-07-27 14:15                     ` Jason McIntyre
     [not found]                       ` <20100728123317.GA43609@edoofus.dev.vega.ru>
2010-07-28 13:38                         ` Jason McIntyre
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=4C4EE52F.9020601@bsd.lv \
    --to=kristaps@bsd.lv \
    --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).