bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #52990] [ms] update warning manipulation to use newer troff default


From: G. Branden Robinson
Subject: [bug #52990] [ms] update warning manipulation to use newer troff default
Date: Sun, 26 Feb 2023 19:55:56 -0500 (EST)

Update of bug #52990 (project groff):

                  Status:                   Fixed => Invalid                
         Planned Release:                  1.23.0 => None                   
                 Summary: Stop the ms macro package from manipulating warnings
=> [ms] update warning manipulation to use newer troff default

    _______________________________________________________

Follow-up Comment #3:

Updating summary and reclassifying this ticket as invalid due to the following
commit, as noted by Ingo in Bjarni in comment #2 and comment #1.


commit 5aa934e701ac96c48cad71eae39ddb5817a7399c
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Thu Feb 6 17:17:38 2020 +1100

    ms: Cease warning level manipulation.
    
    Stop ms macro package from manipulating warnings.
    
    * tmac/s.tmac: Remove code block that attempted to enable all
      warnings "only if none are given on the command line".  It did this by
      simply comparing the value of the warn register (\n[.warn]) against
      the default value; but of course, a user could specify -w options that
      exactly matched the default and the test would not be able to tell,
      causing puzzling and undesired behavior.  Furthermore, the hard-coded
      default was out of date and did not correspond to recent releases of
      groff.  If you want all warnings on, use the ".warn" request with no
      arguments in your ms document or pass "-w w" to groff (see troff(1) or
      the Texinfo manual for more on warnings).
    
    Thanks to Bjarni Ingi Gislason for bringing this issue to our attention.
    
    Resolves <https://savannah.gnu.org/bugs/?57583>.



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?52990>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]