Pedro Andres Aranda Gutierrez <[email protected]> writes:
> The best way to get a reasonable workaround for this would be to use
> the org-file as a basis, generate a LaTeX and then check on that in a
> plain LaTeX environment to then return to Org.
Could you elaborate about what exactly we can check in plain LaTeX environment?
Did you try the example? All LaTeX complains about there is overfill
hbox, which is not a particularly uncommon warning. Moreover, it is
usually more or less harmless, but not in this specific case.
>> >> - contents
>> >> + (or contents "\\leavevmode")
>> >> (let ((case-fold-search t)
>> >
>> > "\\penalty0" may be safer (perhaps with additional "\\relax " or newline
>> > for a case that next portion of text will be started from a number
>> > without any space). I was not aware that penalties are not combined by
>> > TeX, any is considered as a break point. There are various tricks like
>> > \vfil\penalty100\vfilneg to allow variation of page height.
>> >
>> > Maybe e.g. 100 should be used instead of zero to make less probable page
>> > break between section and subsection titles. (Carefully prepared text
>> > likely will have at least a paragraph before next level header. Anyway
>> > nobody expects that early drafts are carefully formatted.)
>
> In the case of an ugly break, a 'manual' \clearpage may be enough (KISS).
If we do \clearpage after each empty section, it sounds too much.
>> What about simply \mbox{}?
>
> \mbox{} may not work if its contents starts to grow.
I suggest adding \mbox{} only when section contents is empty. Or do you
mean some other contents?
--
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>
