Eric S Fraga <e.fr...@ucl.ac.uk> writes:
> Response below/inline for email Pedro Andres Aranda Gutierrez wrote:
>> (original email sent 5 Sep 2025 at 11:50)
>>
>> It's at the beginning of the thread...
>
> Not quite. The beginning of the thread describes the issue with the
> test document. What I am asking about is the purpose of such a document
> (so many sub-levels). Knowing the actual purpose might allow us to
> suggest alternative ways of organising the document, avoiding the
> issue(s) highlighted.
The basic use-case is creating an Org file with lots of tasks, subtasks,
etc. The documentation doesn't really preclude that and, so, you first
inclination might be to start with the big project ("My Life") and just
continually break it down. Understanding the limits of document classes
in LaTeX would lead to changing the structure of my layout -- perhaps by
simply moving large sub*tasks to new files.
The specific use-case was wanting to print an outline of my document to
share with someone (my wife, but it could be a manager or professor).
The quick and dirty approach to doing that was to open the document to a
paricular level without contents and export to PDF with Visibility
On. That, I guess, let to problem of two headers with no contents in
between which you've mentioned. I put the test document together
because my document is not for everyone's consumption.
Ultimately, using a standard option in Org should either do what you
expect or warn you (in execution or in documentation) that it's not
going to work as you expect.
I should run this test case on other export engines to see how they
handle it... :-\
--
David Masterson
