Re: -Tlint parser errors and warnings to stdout

[Kristaps Dzonsons <kristaps@bsd.lv>]

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