You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This results into e.g. code blocks ending with an .IP "" 0, i.e. the opening of a new paragraph, which is left subsequently empty (also: .IP "" 0 is also equivalent to .P, I believe?). In the following excerpt of the test/code_blocks.roff output, one can see that there is the .IP, followed by another .P, meaning that there is an empty paragraph between the two code blocks:
[…]
Some text\.
.IP""4
.nf
Some code\.
.fi
.IP""0
.P
Here's some <pre> text\.
[…]
Finally, it seems that commit f528c25 tried to address the output by using more's -s, to strip the extra vertical whitespace. But, I wonder if instead ronn could just not emit those empty paragraphs?
The text was updated successfully, but these errors were encountered:
I agree with you here. Thanks for doing the analysis. Scheduling this for fix in 0.11 or before. I'm going to have to do some reading on how exactly .IP and .P work.
The code currently reads:
This results into e.g. code blocks ending with an
.IP "" 0
, i.e. the opening of a new paragraph, which is left subsequently empty (also:.IP "" 0
is also equivalent to.P
, I believe?). In the following excerpt of the test/code_blocks.roff output, one can see that there is the.IP
, followed by another.P
, meaning that there is an empty paragraph between the two code blocks:Finally, it seems that commit f528c25 tried to address the output by using more's
-s
, to strip the extra vertical whitespace. But, I wonder if instead ronn could just not emit those empty paragraphs?The text was updated successfully, but these errors were encountered: