Pedro writes:
> How did you know that, should that be mentioned in the corresponding
> section? (I could not find another one) [1] [2].
It is written at the bottom of [2]:
When exporting subtrees, special node properties can override the
above keywords. These properties have an ‘EXPORT_’ p
Hey!
And this is trivial, but it took me a while to figure it out
Of course, if you want to use more than one EXPORT_LATEX_HEADER for that
subtree export, you need to use multi-value property [0]:
:PROPERTIES:
:EXPORT_LATEX_HEADER: \usepackage{bookmark}
:EXPORT_LATEX_HEADER+: \usepackage{nopa
Hi Rudy,
You nailed it!! Using property EXPORT_LATEX_HEADER exactly solves my
problem, thank you very much. For completeness, I will re-attach the
file with the solution
How did you know that, should that be mentioned in the corresponding
section? (I could not find another one) [1] [2]. Mayb
pinm...@cas.cat writes:
I am unsure I understand the problem, as the reproduction file is not
minimal, and I do not have much time on my hands now. That said, the
file says:
> # if you uncomment this, both reports are in landscape
> #+LATEX_HEADER: \usepackage[a4paper, landscape, margin=0.5cm]{g
Hi,
** The context
I found a way to export subtrees to PDF and I liked that idea a lot, I
use it, for example, to generate with an org-capture an invoice, and
export to PDF, etc.
The invoice is part of my journal.
My journal is structured for the whole year (year, week, day). That
file has a l
