Follow-up Comment #1, bug #51482 (project groff): 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 <[email protected]> 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 <[email protected]> --- 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 _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?51482> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/ _______________________________________________ bug-groff mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-groff
