From: Joerg Sonnenberger <joerg@britannica.bec.de>
To: discuss@mdocml.bsd.lv
Subject: Re: mandoc -Tlint -> stdout?
Date: Thu, 24 Mar 2011 22:13:32 +0100 [thread overview]
Message-ID: <20110324211332.GA13346@britannica.bec.de> (raw)
In-Reply-To: <20110324204519.GC25740@iris.usta.de>
On Thu, Mar 24, 2011 at 09:45:19PM +0100, Ingo Schwarze wrote:
> Christian Weisgerber has brought up the idea to have mandoc -Tlint
> send its output to stdout instead of stderr, arguing that in -Tlint
> mode, nothing else is going to stdout and error messages and warnings
> are indeed the intended *output* in that mode.
I disagree. The expected output of -Tlint should always be silence.
As such output is considered diagnostic and go to stderr. If I ever get
a chance to require man page linting as default in the build system, it
certainly makes it much easier to follow if it goes to stderr.
Joerg
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2011-03-24 21:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110324202607.GA51818@lorvorc.mips.inka.de>
2011-03-24 20:45 ` Ingo Schwarze
2011-03-24 21:13 ` Joerg Sonnenberger [this message]
2011-03-25 22:27 ` Ulrich Spörlein
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=20110324211332.GA13346@britannica.bec.de \
--to=joerg@britannica.bec.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).