From: Ingo Schwarze <schwarze@usta.de>
To: discuss@mdocml.bsd.lv
Cc: Christian Weisgerber <naddy@mips.inka.de>
Subject: Re: mandoc -Tlint -> stdout?
Date: Thu, 24 Mar 2011 21:45:19 +0100 [thread overview]
Message-ID: <20110324204519.GC25740@iris.usta.de> (raw)
In-Reply-To: <20110324202607.GA51818@lorvorc.mips.inka.de>
Hi,
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.
An obvious downside is that it introduces a certain asymmetry;
however, i'm not sure that it will ever confuse people.
Of course, there are no big advantages either; maybe the most
important point is that redirecting or piping output becomes
a bit less tedious.
Documenting it will not introduce that much complication,
basically a single sentence regarding -Tlint.
I'm not quite sure, maybe i'm mildly in favour of the idea.
Implementation seems to be relatively simple, basically we would
just need to add the error output stream as a member to struct
curparse.
How do you feel about it?
Yours,
Ingo
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next parent reply other threads:[~2011-03-24 20:45 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 [this message]
2011-03-24 21:13 ` Joerg Sonnenberger
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=20110324204519.GC25740@iris.usta.de \
--to=schwarze@usta.de \
--cc=discuss@mdocml.bsd.lv \
--cc=naddy@mips.inka.de \
/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).