From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp-1.sys.kth.se (smtp-1.sys.kth.se [130.237.32.175]) by krisdoz.my.domain (8.14.3/8.14.3) with ESMTP id p92FCx8h018318 for ; Sun, 2 Oct 2011 11:12:59 -0400 (EDT) Received: from mailscan-1.sys.kth.se (mailscan-1.sys.kth.se [130.237.32.91]) by smtp-1.sys.kth.se (Postfix) with ESMTP id 2E4CA155920; Sun, 2 Oct 2011 17:12:54 +0200 (CEST) X-Virus-Scanned: by amavisd-new at kth.se Received: from smtp-1.sys.kth.se ([130.237.32.175]) by mailscan-1.sys.kth.se (mailscan-1.sys.kth.se [130.237.32.91]) (amavisd-new, port 10024) with LMTP id cC0P1yCzYc8c; Sun, 2 Oct 2011 17:12:53 +0200 (CEST) X-KTH-Auth: kristaps [193.10.49.5] X-KTH-mail-from: kristaps@bsd.lv Received: from [172.16.18.84] (unknown [193.10.49.5]) by smtp-1.sys.kth.se (Postfix) with ESMTP id 0EA821551FC; Sun, 2 Oct 2011 17:12:53 +0200 (CEST) Message-ID: <4E887F74.3030808@bsd.lv> Date: Sun, 02 Oct 2011 17:12:52 +0200 From: Kristaps Dzonsons User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110820 Icedove/3.1.12 X-Mailinglist: mdocml-tech Reply-To: tech@mdocml.bsd.lv MIME-Version: 1.0 To: tech@mdocml.bsd.lv CC: Ingo Schwarze , naddy@openbsd.org Subject: Re: -Tlint parser errors and warnings to stdout 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> In-Reply-To: <20110928092146.GA5320@iris.usta.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 09/28/2011 11:21 AM, Ingo Schwarze wrote: > Hi, > > 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. Thanks, Kristaps -- To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv