bugGNU troff - Bugs: bug #51482, [PATCH] test-groff.in: Add options...

 
 

bug #51482: [PATCH] test-groff.in: Add options enabling warnings and backtrace

Submitted by:  Bjarni Ingi Gislason <bjarniig>
Submitted on:  Sun 16 Jul 2017 08:04:54 PM UTC  
 
Category:  None Severity:  3 - Normal
Item Group:  None Status:  Fixed
Privacy:  Public Assigned to:  G. Branden Robinson <gbranden>
Open/Closed:  Closed Planned Release:  None

Add a New Comment (Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Sat 18 Nov 2017 11:18:00 PM UTC, comment #2: 

The part of this that applies to troff(1) is a duplicate of Savannah #47784, according to Bertrand's commit 8ca41399a2449fe5d619a6edd292c127c891f4e7 (28 August).

G. Branden Robinson <gbranden>
Project MemberIn charge of this item.
Sun 16 Jul 2017 08:07:52 PM UTC, comment #1: 

  Forgot to add "minus vervatim minus" at the end of patch for the web-page

From 8c8036707fea01b4f415da083ae3f19d70ddb3eb Mon Sep 17 00:00:00 2001
From: Bjarni Ingi Gislason <bjarniig@rhi.hi.is>
Date: Sun, 16 Jul 2017 19:55:24 +0000
Subject: [PATCH] test-groff.in; troff.1.man: Add options for warnings and
backtrace; change "-w all" to " -ww"

  This is a test version, so as much code as possible should be used by
default.

  Actually all warnings should be enabled by default; the current default
choice is simple an illusion, telling people everything is o.k., when it
actually is not always the case.

  This is also a contradiction, maintainers have created warnings, and yet
silence them (no free speech, must be extra asked for).

  How do people already know that every input they use is already free of
errors, bad constructs etc.

  Does your experience proof that every man-page (source file) is free of
everything that "groff" is constructed to warn about?

  Is this philosophy "all warnings are equal but some are more equal than
others", a good one, a fundamental one, a paradigm in computer science?

Signed-off-by: Bjarni Ingi Gislason <bjarniig@rhi.hi.is>
---
src/roff/troff/troff.1.man | 2 +-
test-groff.in              | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/roff/troff/troff.1.man b/src/roff/troff/troff.1.man
index 0df947bb..bc9b51b0 100644
--- a/src/roff/troff/troff.1.man
+++ b/src/roff/troff/troff.1.man
@@ -299,7 +299,7 @@ below.
.
For example, to enable all warnings, use
.B \-w
-.BR all .
+.BR w .
Multiple
.B \-w
options are allowed.
diff --git a/test-groff.in b/test-groff.in
index 953299b6..357c3352 100644
--- a/test-groff.in
+++ b/test-groff.in
@@ -38,4 +38,4 @@ GROFF_FONT_PATH=$builddir/font$SEP$srcdir/font
GROFF_TMAC_PATH=$srcdir/tmac$SEP$builddir/tmac$SEP$srcdir/contrib/mom$SEP$builddir/contrib/mom
export GROFF_BIN_PATH GROFF_COMMAND_PREFIX GROFF_FONT_PATH GROFF_TMAC_PATH

-exec $builddir/groff ${1+"$@"}
+exec $builddir/groff -b -ww ${1+"$@"}
--
2.13.2

Bjarni Ingi Gislason <bjarniig>
Sun 16 Jul 2017 08:04:54 PM UTC, original submission:  

  Actually all warnings should be enabled by default; the current default
choice is simple an illusion, telling people everything is o.k., when it
actually is not always the case.

  This is also a contradiction, maintainers have created warnings, and yet
silence them (no free speech, must be extra asked for).

  How do people already know that every input they use is already free of
errors, bad constructs etc.

  Does your experience proof that every man-page (source file) is free of
everything that "groff" is constructed to warn about?

  Is this philosophy "all warnings are equal but some are more equal than
others", a good one, a fundamental one, a paradigm in computer science?

Bjarni Ingi Gislason <bjarniig>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by bgarrigues (Updated the item)
  • -email is unavailable- added by gbranden (Updated the item)
  • -email is unavailable- added by bjarniig (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

     

     

    Follow 6 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-07-02 bgarrigues Open/ClosedOpen => Closed
    2017-11-18 gbranden StatusIn Progress => Fixed
    2017-11-18 gbranden Summary[PATCH] test-groff.in; troff.1.man: Add options for warnings and backtrace; change "-w all" to " -ww" => [PATCH] test-groff.in: Add options enabling warnings and backtrace
    2017-11-18 gbranden StatusNone => In Progress
        Assigned toNone => gbranden
    2017-11-10 gbranden SummaryPATCH] test-groff.in; troff.1.man: Add options for warnings and backtrace; change "-w all" to " -ww" => [PATCH] test-groff.in; troff.1.man: Add options for warnings and backtrace; change "-w all" to " -ww"

    Back to the top


    Powered by Savane 3.5