Re: [BUG] "\fC" macro in ox-man.el [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.2/lisp/org/)]

[Ihor Radchenko <yantar92@posteo.net>]

"onf" <onf@disroot.org> writes:

>> Also, what if we leave \fC and add \f[CR]/.EX on top?
>> AFAIU, the worst case scenario for \fC is that it does nothing. By
>> leaving it there, we thus retain old working exports working while also
>> adding appropriate format when \f[CR] is supported.
>
> The \f escape sets current font. \fP restores previous font.
> What this means is that doing \fC\f[CR]Lorem\fP:
>  (1) sets the text Lorem in Courier if font name C or CR exists
>  (2) restores previous font if neither font C nor CR exists
>  (3) sets font to Courier if both font name C and CR exist

What about \fC\f[CR]Lorem\fP\fP?

>> Do I understand correctly that blank line is sometimes interpreted as
>> vertical spacing and sometimes ignored?
>
> A blank input line is equivalent to .sp unless the .blm request was called
> to change this behavior. .blm is groff's invention (see groff_diff(7)).

Then maybe we can put .sp explicitly instead of a blank line.
In our code, we add blank after blocks (or displays) of code. Extra
vertical space after seems to be reasonable.

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>