[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #52463] anything that talks to standard error should identify itsel
From: |
G. Branden Robinson |
Subject: |
[bug #52463] anything that talks to standard error should identify itself |
Date: |
Sun, 19 Nov 2017 23:26:46 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 |
URL:
<http://savannah.gnu.org/bugs/?52463>
Summary: anything that talks to standard error should
identify itself
Project: GNU troff
Submitted by: gbranden
Submitted on: Mon 20 Nov 2017 04:26:45 AM UTC
Category: None
Severity: 1 - Wish
Item Group: Wishlist
Status: None
Privacy: Public
Assigned to: gbranden
Open/Closed: Open
Discussion Lock: Any
Planned Release: None
_______________________________________________________
Details:
Many parts of groff (especially preprocessors and macro packages) emit
diagnostics to standard error without identifying where they are coming from.
As groff lends itself to deep pipelines and is an interpreted, extensible
language on top of that, it's frustrating to not know which part of the system
is barking at me when there is a problem.
I propose to make all tools and macro packages identify themselves when
writing to stderr or using .ab, .tm, etc., if they do not already.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?52463>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [bug #52463] anything that talks to standard error should identify itself,
G. Branden Robinson <=