Fix bug handling escape code at end of a line.

When scan_troff expands an escape, it calls FLUSHIBP, which
nukes all previous context. If the escape is subsequently
followed by a newline, it looks like the newline at the start
of a line, which is consumed. There is a subtlety there that
we also want to preserve a newline after an escape in
preformatted mode.

This fix addresses at least two issues in the TXR Man page.
One is that occurrences of the \*(TL and \*(TX at the ends of
lines are causing run-on output: the expansion gets glued to
the word which follows in the next line. The other issue
is that in some code exmaple blocks, lines ending in a
backslash (encoded as the \e escape) are being joined.

0 files changed, 0 insertions, 0 deletions