Follow-up Comment #5, bug #63028 (group groff): [comment #0 original submission:] > they should think about the order in which they specify the > characters, as only the last one is likely to end up visible.
An exception is (at least some) space-like characters. $ echo "\o'abcd'efg" | nroff | cat -s defg $ echo "\o'abc\0'efg" | nroff | cat -s cefg $ echo "\o'abc\ 'efg" | nroff | cat -s cefg Groff and Heirloom's nroff produce identical results with those inputs. Where they diverge is when \o is given an ordinary space: $ echo "\o'abc 'efg" | nroff | cat -s troff:<standard input>:1: error: expected ordinary or special character, got a space cefg Heirloom nroff's output is the same, but it doesn't throw the error. If that holds of ancestor nroffs as well, groff objecting to this formerly permitted construction should be documented in groff_diff(7). _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?63028> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/