Follow-up Comment #18, bug #67992 (group groff):

I may get back to the philosophical stuff in comment #17 later, but for now I
wanted to note that:

Prefixing the device extension escape sequences with `\c` restores _groff_
1.23.0-ish behavior for all three macro packages.


$ printf '\\X"pdf: xrev"\n' | ~/groff-1.23.0/bin/groff -me -a
<beginning of page>

$ printf '\\X"pdf: xrev"\n' | ~/groff-1.23.0/bin/groff -mm -a
<beginning of page>
 - 1 - 
  

  
  
  
$ printf '\\X"pdf: xrev"\n' | ~/groff-1.23.0/bin/groff -ms -a
<beginning of page>

  
$ printf '\\c\\X"pdf: xrev"\n' | ./build/test-groff -me -a
<beginning of page>

$ printf '\\c\\X"pdf: xrev"\n' | ./build/test-groff -mm -a
<beginning of page>
 - 1 - 
  

  
  
  
$ printf '\\c\\X"pdf: xrev"\n' | ./build/test-groff -ms -a
<beginning of page>




Playing around with the input stream pointer did not make anything better, and
always much worse.

So I think I'm on the right track with my other hypothesis of device extension
commands needing to "start the document" if they occur before the document has
started.

If so, bug #65977 would be implicated.  Maybe I didn't completely fix it.


    _______________________________________________________

Reply to this item at:

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

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

Attachment: signature.asc
Description: PGP signature

Reply via email to