URL:
  <https://savannah.gnu.org/bugs/?67219>

                 Summary: New warning text sometimes less specific about
reason for unadjustability
                   Group: GNU roff
               Submitter: barx
               Submitted: Mon 16 Jun 2025 12:56:45 AM CDT
                Category: Core
                Severity: 2 - Minor
              Item Group: Warning/Suspicious behaviour
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Mon 16 Jun 2025 12:56:45 AM CDT By: Dave <barx>
Groff's warning text used to distinguish between being unable to adjust a line
because it was unbreakable and being unable to adjust a line for some other
reason.

$ cat breakwarn
.ll 1i
aaaaaaaaaaaaaaaaa
aaaaaaaa aaaaaaaa
$ groff -z breakwarn
troff:breakwarn:2: warning [p 1, 0.0i]: cannot break line
troff:breakwarn:3: warning [p 1, 0.2i]: cannot adjust line
$ groff-latest -z breakwarn
troff:breakwarn:2: warning [page 1, 0.0i]: cannot adjust line; overset by
0.0483333i
troff:breakwarn:3: warning [page 1, 0.2i]: cannot adjust line; underset by
0.506667i

Quantifying the issue is certainly more informative.  And it's possible the
wording change is intentional: it's true that the line both cannot be broken
and cannot be adjusted.  If so, this bug can be rejected.

However, there are various reasons a line might not be adjustable, and being
unbreakable is only one of them.  So the former wording, "cannot break," was
more specific.

This is very likely a consequence of
[http://git.savannah.gnu.org/cgit/groff.git/commit/?id=82192662b commit
82192662b].  The new code appears to choose between the words "adjust" and
"break" based on a condition that doesn't take the full situation into
account.







    _______________________________________________________

Reply to this item at:

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

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

Attachment: signature.asc
Description: PGP signature

Reply via email to