From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from scc-mailout.scc.kit.edu (scc-mailout.scc.kit.edu [129.13.185.201]) by krisdoz.my.domain (8.14.3/8.14.3) with ESMTP id p2OKjOce031926 for ; Thu, 24 Mar 2011 16:45:26 -0400 (EDT) Received: from hekate.usta.de (asta-nat.asta.uni-karlsruhe.de [172.22.63.82]) by scc-mailout-01.scc.kit.edu with esmtp (Exim 4.72 #1) id 1Q2rPE-0005zF-CU; Thu, 24 Mar 2011 21:45:23 +0100 Received: from donnerwolke.usta.de ([172.24.96.3]) by hekate.usta.de with esmtp (Exim 4.72) (envelope-from ) id 1Q2rPE-0005xO-Ea; Thu, 24 Mar 2011 21:45:20 +0100 Received: from iris.usta.de ([172.24.96.5] helo=usta.de) by donnerwolke.usta.de with esmtp (Exim 4.69) (envelope-from ) id 1Q2rPE-00048y-D8; Thu, 24 Mar 2011 21:45:20 +0100 Received: from schwarze by usta.de with local (Exim 4.72) (envelope-from ) id 1Q2rPE-0005Tl-6P; Thu, 24 Mar 2011 21:45:20 +0100 Date: Thu, 24 Mar 2011 21:45:19 +0100 From: Ingo Schwarze To: discuss@mdocml.bsd.lv Cc: Christian Weisgerber Subject: Re: mandoc -Tlint -> stdout? Message-ID: <20110324204519.GC25740@iris.usta.de> References: <20110324202607.GA51818@lorvorc.mips.inka.de> X-Mailinglist: mdocml-discuss Reply-To: discuss@mdocml.bsd.lv MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110324202607.GA51818@lorvorc.mips.inka.de> User-Agent: Mutt/1.5.21 (2010-09-15) 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