bug-groff
[Top][All Lists]
Advanced

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

[bug #66526] GNU troff misinterprets conditional expressions starting wi


From: G. Branden Robinson
Subject: [bug #66526] GNU troff misinterprets conditional expressions starting with `|`
Date: Wed, 4 Dec 2024 04:22:44 -0500 (EST)

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

                 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
                Severity: 3 - Normal
              Item Group: Incorrect behaviour
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Wed 04 Dec 2024 09:22:40 AM UTC By: G. Branden Robinson <gbranden>
-- A Platonic semi-dialogue --

Is one inch greater than zero?


$ printf '.ie |1i>0 .tm yes\n.el .tm no\n' | ./build/test-groff -ww
troff:<standard input>:1: warning: missing closing delimiter in output
comparison operator; expected character '|', got a newline
no


Damn it, Branden, your naïve and ill-considered so-called reforms to _groff_
break everything everywhere all the time and I'm sick of it.  You should
resign as maintainer.


$ printf '.ie |1i>0 .tm yes\n.el .tm no\n' | ~/groff-1.23.0/bin/groff -ww
troff:<standard input>:1: warning: missing closing delimiter in output
comparison operator (got a newline)
no


I've had it up to here!  Just sick of your nonsense.  Seven years of long
emails, obscure jokes, and detestable politics.  When Trump's hillbilly MAGA
squads beat you to a pulp, I'll laugh.


$ printf '.ie |1i>0 .tm yes\n.el .tm no\n' | ~/groff-1.22.4/bin/groff -ww
troff: <standard input>:1: warning: missing closing delimiter
no


Wait--hang on...


$ printf '.ie |1i>0 .tm yes\n.el .tm no\n' | ~/groff-1.22.3/bin/groff -ww
<standard input>:1: warning: missing closing delimiter
no


STOP!  Yeah, well, I never liked _groff_ anyway.


$ printf '.ie |1i>0 .tm yes\n.el .tm no\n' | ~/heirloom/bin/nroff 
yes
$ printf '.ie |1i>0 .tm yes\n.el .tm no\n' | DWBHOME=~/dwb ~/dwb/bin/nroff 
yes
$ pdp11 ./boot.simh 

PDP-11 simulator V3.8-1
Disabling XQ
@boot
New Boot, known devices are hp ht rk rl rp tm vt 
: rl(0,0)rl2unix
mem = 177856
# Restricted rights: Use, duplication, or disclosure
is subject to restrictions stated in your contract with
Western Electric Company, Inc.
Thu Sep 22 23:16:01 EDT 1988

login: dmr
$ nroff <<EOF
> .ie |1i>0 .tm yes
> .el .tm no
> EOF
yes
$ 
login: 
Simulation stopped, PC: 002306 (MOV (SP)+,177776)
sim> quit
Goodbye


See?!  Other troffs are better and always have been.  I haven't typeset
anything in 20 years, or maybe ever, but one day I will, and my links won't be
pointing anywhere you have anything to do with!

I'd rather be using Seventh Edition anyway than any of this kopyleft krap!  I
know who the thought leaders are and I'll be following _them_.  Brogrammer
strong!

--end of semi-dialogue--

So, _melodramatis personae_ aside, this goes way back.  And apparently has
seldom or never been noticed or remarked upon.  I think it constitutes further
evidence that GNU _troff_ should retire support for "weird" delimiters, except
in AT&T compatibility mode.  See bug #66009.







    _______________________________________________________

Reply to this item at:

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

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

Attachment: signature.asc
Description: PGP signature


reply via email to

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