[bug #66009] [troff] accepts `|` as operand delimiter, but should not

Follow-up Comment #3, bug #66009 (group groff): When is a delimiter not a delimiter? When it's `|`, apparently. See bug #66526. ...which is arguably the same issue as I identified in comment #0, but explored in a different way. In that bug, I'll deal with special-casing `|` at the start of a c

[bug #66526] GNU troff misinterprets conditional expressions starting with `|`

Update of bug #66526 (group groff): Status:None => In Progress Assigned to:None => gbranden ___ Reply to this item at: __

[bug #66504] [gropdf] build failure on Solaris 10

Update of bug #66504 (group groff): Status: Need Info => In Progress ___ Reply to this item at: ___ Message sent via Sav

[bug #66504] [gropdf] build failure on Solaris 10

Update of bug #66504 (group groff): Status: In Progress => Need Info ___ Follow-up Comment #9: Err, no, I'm wrong. Sorry. I'm still getting two Perl warnings. gropdf: warning: Perl module 'Compress::Zlib'

[bug #66504] [gropdf] build failure on Solaris 10

Follow-up Comment #10, bug #66504 (group groff): I can apply the same fix as the one you suggested; if the scalars `P` and `St` are uninitialized, just set them to null strings. I'll see if that makes headway, but I want your advice too as I'm flying pretty blindly with the _gropdf_ code. _

[bug #66526] GNU troff misinterprets conditional expressions starting with `|`

URL: Summary: GNU troff misinterprets conditional expressions starting with `|` Group: GNU roff Submitter: gbranden Submitted: Wed 04 Dec 2024 09:22:40 AM UTC Category: Core

[bug #66504] [gropdf] build failure on Solaris 10

Follow-up Comment #12, bug #66504 (group groff): Wait, that's truncated. Sorry. Here's the full patch. diff --git a/ChangeLog b/ChangeLog index 332df7884..f73133de4 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,11 @@ +2024-12-03 Deri James + + * src/devices/gropdf/gropdf.pl: Use P

[bug #66504] [gropdf] build failure on Solaris 10

Follow-up Comment #11, bug #66504 (group groff): Hi Deri, This amended patch seems to quiet the warnings. Please review for correctness. I grasp that the code here is processing a _grout_ 'x' command, but am not sure I have preserved the desired logic. diff --git a/src/devices/gropdf/gropdf.p

[bug #66526] GNU troff misinterprets conditional expressions starting with `|`

Follow-up Comment #1, bug #66526 (group groff): $ groff --version | head -1 GNU groff version 1.19.2 $ printf '.ie |1i>0 .tm yes\n.el .tm no\n' | groff -ww :1: warning: missing closing delimiter no ___ Reply to this item at:

[bug #66504] [gropdf] build failure on Solaris 10

Follow-up Comment #8, bug #66504 (group groff): Hi Deri, At 2024-12-03T19:19:11-0500, Deri James wrote: > For the 'uninitialised' warnings try inserting this line after line > 2018:- > > $xprm[4]='' if !defined($xprm[4]); Works like a charm. I'll push this, with you as --author of course. > I

[bug #66526] GNU troff misinterprets conditional expressions starting with `|`

Update of bug #66526 (group groff): Status: In Progress => Fixed Open/Closed:Open => Closed Planned Release:None => 1.24.0 ___ Follow-up Comment #2: