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 p93MQ83X017718 for ; Mon, 3 Oct 2011 18:26:09 -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 1RAqxb-0005b3-VX; Tue, 04 Oct 2011 00:26:07 +0200 Received: from donnerwolke.usta.de ([172.24.96.3]) by hekate.usta.de with esmtp (Exim 4.72) (envelope-from ) id 1RAqxb-0002dg-W1; Tue, 04 Oct 2011 00:26:07 +0200 Received: from iris.usta.de ([172.24.96.5] helo=usta.de) by donnerwolke.usta.de with esmtp (Exim 4.72) (envelope-from ) id 1RAqxb-0004xV-Uz; Tue, 04 Oct 2011 00:26:07 +0200 Received: from schwarze by usta.de with local (Exim 4.72) (envelope-from ) id 1RAqxb-0005z6-Tz; Tue, 04 Oct 2011 00:26:07 +0200 Date: Tue, 4 Oct 2011 00:26:07 +0200 From: Ingo Schwarze To: tech@mdocml.bsd.lv Cc: naddy@openbsd.org Subject: Re: -Tlint parser errors and warnings to stdout Message-ID: <20111003222607.GI20053@iris.usta.de> References: <20110925101243.GC4867@iris.usta.de> <20110925111746.GA14018@lain.home> <20110925180227.GJ4867@iris.usta.de> <20110925182641.GA26028@britannica.bec.de> <4E810578.7040008@bsd.lv> <20110927051427.GA16670@britannica.bec.de> <20110928092146.GA5320@iris.usta.de> <4E887F74.3030808@bsd.lv> X-Mailinglist: mdocml-tech Reply-To: tech@mdocml.bsd.lv MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E887F74.3030808@bsd.lv> User-Agent: Mutt/1.5.21 (2010-09-15) Hi Kristaps, Kristaps Dzonsons wrote on Sun, Oct 02, 2011 at 05:12:52PM +0200: > On 09/28/2011 11:21 AM, Ingo Schwarze wrote: >> Joerg Sonnenberger wrote on Tue, Sep 27, 2011 at 07:14:27AM +0200: >>> On Tue, Sep 27, 2011 at 01:06:32AM +0200, Kristaps Dzonsons wrote: >>>> The -Tlint thing is a different story. At first I thought (Ingo >>>> will recognise this behaviour) No Way In Hell. But (1) mdoclint in >>>> regress pushes to stdout; (2) lint itself pushes to stdout; and (3) >>>> there's no real notion of portability/compat so we can do what works >>>> best for us. So basically I'm fine with sticking a dup2 in there if >>>> people think it will save time and effort. >>> ...or do some refactoring and replace stderr with errout and just >>> reassign the variable? >> Here is a patch doing it in about that way, only slightly different. >> Restore the half-removed curparse argument to mandocmsg(), >> than use that to either select stderr or stdout >> for parser diagnostic output. > Let's hold off on this for a little bit, as there are some elements > that need thought before going down this road (which I'm ok with, I > should clarify). Foremost, since mandoc.3 is built to be a library > upstream, system errors should be reporting by the same (or > parallel) interface as mandoc parse errors---NOT using perror or > whatnot. This has bugged me for a while, but I've not had the > motivation to fix it---let me do so before we continue along this > road. No problem, so i'm postponing my patch until you have done the cleanup. No particular hurry, but if we want to do it, i think we should get it off the table until about the end of the year, to not get too close to the 5.1 release phase. Yours, Ingo -- To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv