Update of bug #64300 (group groff):

                  Status:               Need Info => Confirmed

    _______________________________________________________

Follow-up Comment #6:

I think we should just ignore an `sp` request when we're off the page;
equivalently, when the value of the `nl` register is `-1`.

No GNU _troff_ request *apart* from `sp` that has distinct no-break control
character semantics advances onto the page when invoked thus.


 $ for req in br brp ce cf fi fl in nf rj sp; do echo '***' $req; printf
"'%s\n.pnr nl\n" "$req" | ~/groff-HEAD/bin/groff -Z; done
*** br
nl      -1      +0      0
*** brp
nl      -1      +0      0
*** ce
nl      -1      +0      0
*** cf
nl      -1      +0      0
*** fi
nl      -1      +0      0
*** fl
nl      -1      +0      0
*** in
nl      -1      +0      0
*** nf
nl      -1      +0      0
*** rj
nl      -1      +0      0
*** sp
x T ps
x res 72000 1 1
x init
p1
nl      0       +0      0
x trailer
V792000
x stop


Even supplying an argument to the request, giving it more meat to chew,
changes nothing.


$ for req in br brp ce cf fi fl in nf rj sp; do echo '***' $req; printf "'%s
1\n.pnr nl\n" "$req" | ~/groff-HEAD/bin/groff -Z; done
*** br
nl      -1      +0      0
*** brp
nl      -1      +0      0
*** ce
nl      -1      +0      0
*** cf
troff:<standard input>:1: error: file throughput request is not allowed in
safer mode
nl      -1      +0      0
*** fi
nl      -1      +0      0
*** fl
nl      -1      +0      0
*** in
nl      -1      +0      0
*** nf
nl      -1      +0      0
*** rj
nl      -1      +0      0
*** sp
x T ps
x res 72000 1 1
x init
p1
nl      0       +0      0
x trailer
V792000
x stop


(`cf`'s squawk can be ignored; unlike the others that accept an argument, its
argument is not a measurement or count.)

We can have `sp` throw a warning if it's called with the no-break control
character when the drawing position is not on the page.  If I can't find a
warning category that fits well, I'll make it an error.


    _______________________________________________________

Reply to this item at:

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

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


Reply via email to