discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Kristaps Dzonsons <kristaps@bsd.lv>
To: discuss@mdocml.bsd.lv
Subject: Re: pending open issues
Date: Tue, 27 Jul 2010 11:32:16 +0200	[thread overview]
Message-ID: <4C4EA7A0.1040104@bsd.lv> (raw)
In-Reply-To: <20100727092007.GA21455@bramka.kerhand.co.uk>

>>> ps kristaps, did you spot the mail where i asked about why EXIT STATUS
>>> was being recommended (in mdoc.7)? i need to know where that comes from...
>> Jason (note this is cross-posted to discuss@),
>>
>> EXIT STATUS comes from NetBSD groff's mdoc.template:
>>
>> .\" This next request is for sections 1 and 8 exit statuses only.
>> .\" .Sh EXIT STATUS
>>
>> If this is something they use a lot (Joerg?), then it needs to stay in 
>> with a specific note that NetBSD conventionally uses EXIT STATUS, whilst 
>> OpenBSD puts the `Ex -std' on the final line of the DESCRIPTION.  Not 
>> sure about FreeBSD and DragonFly.  Comments?
>>
> 
> ok. but your mdoc(7) page states this:
> 
> 	EXIT STATUS
>         Command exit status for section 1, 6, and 8 manuals.  This
>         section is the dual of RETURN VALUES, which is used for
>         functions.  Historically, this information was described
>         in DIAGNOSTICS, a practise that is now discouraged.

I think you're looking at mandoc's old EXIT STATUS documentation...

The on-line manuals for DragonFly and Free only mention DIAGNOSTICS 
(just checked), which says that `Ex' should be used there.

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

  reply	other threads:[~2010-07-27  9:31 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 [this message]
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
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=4C4EA7A0.1040104@bsd.lv \
    --to=kristaps@bsd.lv \
    --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).