discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: discuss@mdocml.bsd.lv
Cc: Ruslan Ermilov <ru@FreeBSD.org>
Subject: Re: mdoc EXIT STATUS (Was: pending open issues)
Date: Tue, 3 Aug 2010 23:28:54 +0200	[thread overview]
Message-ID: <20100803212854.GC31307@iris.usta.de> (raw)
In-Reply-To: <20100728133842.GB31150@bramka.kerhand.co.uk>

Hi,

the exchange of information and opinions where to best put exit status
documentation for section 1, 6, and 8 manuals seems unfinished to me;
if i understand correctly, what FreeBSD and DragonFly want and do is
plain enough (EXIT STATUS), but in NetBSD and OpenBSD, i find such
information sometimes in DESCRIPTION, sometimes in DIAGNOSTICS.

However, i'm not trying to settle that question today, right in the
middle of the OpenBSD release process.  Right now, i'm just proposing
a preliminary patch documenting the status quo, which will hopefully
not remain the last word on this matter.

I think it is a bad idea to tell people without any reservation
they should use EXIT STATUS when actually, two systems do not
use that section - no matter whether that is "at all" or "not yet".

OK to commit this for now?

Yours,
  Ingo


Index: mdoc.7
===================================================================
RCS file: /cvs/src/share/man/man7/mdoc.7,v
retrieving revision 1.46
diff -u -p -r1.46 mdoc.7
--- mdoc.7	3 Aug 2010 00:07:57 -0000	1.46
+++ mdoc.7	3 Aug 2010 20:57:39 -0000
@@ -347,7 +347,7 @@ utility processes files ...
 \&.\e\*q The next is for sections 1, 6, 7, & 8 only.
 \&.\e\*q .Sh ENVIRONMENT
 \&.\e\*q .Sh FILES
-\&.\e\*q The next is for sections 1 & 8 only.
+\&.\e\*q The next is for sections 1, 6 & 8 only.
 \&.\e\*q .Sh EXIT STATUS
 \&.\e\*q .Sh EXAMPLES
 \&.\e\*q The next is for sections 1, 4, 6, 7, & 8 only.
@@ -514,11 +514,20 @@ the file is used (created, modified, etc
 See
 .Sx \&Pa .
 .It Em EXIT STATUS
-This section documents the
+Some operating systems, for example
+.Fx
+and
+.Dx ,
+use this section to document the
 command exit status for section 1, 6, and 8 utilities.
-Historically, this information was described in
-.Em DIAGNOSTICS ,
-a practise that is now discouraged.
+Others, for example
+.Nx
+and
+.Ox ,
+show the same information in the
+.Em DIAGNOSTICS
+section or near the end of the
+.Em DESCRIPTION .
 .Pp
 See
 .Sx \&Ex .
@@ -528,11 +537,8 @@ This often contains snippets of well-for
 Make sure that examples work properly!
 .It Em DIAGNOSTICS
 Documents error conditions.
-This is most useful in section 4 manuals.
-Historically, this section was used in place of
-.Em EXIT STATUS
-for manuals in sections 1, 6, and 8; however, this practise is
-discouraged.
+This is most useful in section 4 manuals,
+but sometimes also used for section 1, 6, and 8 utilities.
 .Pp
 See
 .Sx \&Bl
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2010-08-03 21:28 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
2010-08-03 21:28                           ` Ingo Schwarze [this message]
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=20100803212854.GC31307@iris.usta.de \
    --to=schwarze@usta.de \
    --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).