discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Jason McIntyre <jmc@kerhand.co.uk>
To: discuss@mdocml.bsd.lv
Subject: Re: pending open issues
Date: Tue, 27 Jul 2010 11:17:51 +0059	[thread overview]
Message-ID: <20100727101815.GD21455@bramka.kerhand.co.uk> (raw)
In-Reply-To: <4C4EAEE9.9000106@bsd.lv>

On Tue, Jul 27, 2010 at 12:03:21PM +0200, Kristaps Dzonsons wrote:
> 
> Ah, my error... I thought you were talking to Free/DragonFly.  The 
> mandoc page hasn't changed for these sections.
> 
> I'm pretty sure that this reasoning is my own, based on the existence of 
> EXIT STATUS in NetBSD groff manuals.  This was probably before I knew of 
> the balkanisation of mdoc.samples.
> 
> 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.

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

  reply	other threads:[~2010-07-27 10:18 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   ` 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 [this message]
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
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=20100727101815.GD21455@bramka.kerhand.co.uk \
    --to=jmc@kerhand.co.uk \
    --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).