[bug #68357] [troff] doesn't enforce space between `dt` and `wh` request arguments

"G. Branden Robinson" <[email protected]>
Newsgroups gmane.comp.printing.groff.bugs
Message-ID <[email protected]>
Update of bug #68357 (group groff):

                  Status:             In Progress => Fixed
             Open/Closed:                    Open => Closed
         Planned Release:                    None => 1.25.0

    _______________________________________________________

Follow-up Comment #5:


commit ab7f903e168ce0fc04b0eb6cde10be273d9e4e08
Author: G. Branden Robinson <[email protected]>
Date:   Thu May 28 15:11:08 2026 -0500

    [groff]: Regression-test Savannah #68357.
    
    * src/roff/groff/tests/error-no-space-between-dt-or-wh-arguments.sh: Do
      it.
    
    * src/roff/groff/groff.am (groff_TESTS): Run test.
    
    Test fails at this commit.

commit ab462a20e93017c8e656741f7fcc4590e925535b
Author: G. Branden Robinson <[email protected]>
Date:   Thu May 28 15:44:10 2026 -0500

    [troff]: Fix Savannah #68357.
    
    * src/roff/troff/div.cpp (when_request, diversion_trap_request):
      Enforce space requirement between first and second arguments to `wh`
      and `dt` requests.
    
    * doc/groff.texi.in (Other Differences):
    * man/groff_diff.7.man (Other differences):
    * NEWS: Document this behavioral difference from AT&T troffs.
    
    Fixes <https://savannah.gnu.org/bugs/?68357>.  Problem appers to date
    back to groff's birth.




    _______________________________________________________

Reply to this item at:

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

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc (application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQQk97aszIMMAvLLwm6qLAuaBUf3TgUCahknSQAKCRCqLAuaBUf3
TiRgAP98aXN7FiwxPRguhrGtcMSaYh+A9cct2XW9Ff3ug++ZvQEAl2m3NwUCku8c
CVH3Ze2dECRrrQ4vfMQXb0RO33wFeA0=
=ubss
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.