Dominik Schrempf writes:
> Hello,
>
> are you looking for, e.g.,
>
> #+latex_header: \addbibresource{bibliography.bib}
> #+latex_header_extra: do some stuff
> #+latex_header_extra: and even more
>
> I don't use the EXPORT keyword at the beginning, I am not sure if it is
> needed.
>
> Best,
>
On Tuesday, 16 Jun 2020 at 10:46, Alan Schmitt wrote:
> You're right, it should work in a single line. I don't what I did that
> made it fail, and I no longer can reproduce it. Sorry for the noise.
Glad you solved it!
--
: Eric S Fraga via Emacs 28.0.50, Org release_9.3.7-636-gaa32f6
Hello Eric,
On 2020-06-15 10:20, Eric S Fraga writes:
> On Saturday, 13 Jun 2020 at 17:02, Alan Schmitt wrote:
>> This is the crux of the issue: there does not seem to be any way to
>> generate a multi-line header. And this causes problems with LaTeX.
>
> Is the problem solvable in LaTeX? Does
On Saturday, 13 Jun 2020 at 17:02, Alan Schmitt wrote:
> This is the crux of the issue: there does not seem to be any way to
> generate a multi-line header. And this causes problems with LaTeX.
Is the problem solvable in LaTeX? Does \makeatletter expect to be on a
single line? As I said before,
Hello,
On 2020-06-12 16:01, Eric S Fraga writes:
> The snippet from the OP will collate all three LaTeX header lines into a
> single line on export, which is expected in terms of org's
> behaviour. This appears to cause problems with LaTeX, which is maybe
> expected or not; I don't know what
> I am not sure I understand your question. Sorry.
You read my mind.
>
> The snippet from the OP will collate all three LaTeX header lines into a
> single line on export, which is expected in terms of org's
> behaviour.
This is exactly what I was referring to. If the behavior of
On Friday, 12 Jun 2020 at 16:47, Jeremie Juste wrote:
> Many thanks for the info. So, with respect the original post, the behavior of
> the following
> code is to be expected?
I am not sure I understand your question. Sorry.
The snippet from the OP will collate all three LaTeX header lines
Eric S Fraga writes:
>
> This is a standard syntax for adding values to a property. From the info
> manual:
>
> If you want to add to the value of an existing property, append a ‘+’ to
> the property name. The following results in the property ‘var’ having
> the value ‘foo=1 bar=2’.
>
>
On Friday, 12 Jun 2020 at 14:01, Jeremie Juste wrote:
> But I have some more questions. I can see the :EXPORT_LATEX_HEADER in
> the properties menu. (C-x p) but how did you even find :EXPORT_LATEX_HEADER+
> property name?
This is a standard syntax for adding values to a property. From the info
Hello,
can reproduce the issue with
* hello
:PROPERTIES:
:EXPORT_LATEX_HEADER: \makeatletter
:EXPORT_LATEX_HEADER+: \@setplength{refvpos}{\useplength{toaddrvpos}}
:EXPORT_LATEX_HEADER+: \makeatother
:END:
But I have some more questions. I can see the :EXPORT_LATEX_HEADER in
the
Hello Dominik,
On 2020-06-12 10:31, Dominik Schrempf writes:
> are you looking for, e.g.,
>
> #+latex_header: \addbibresource{bibliography.bib}
> #+latex_header_extra: do some stuff
> #+latex_header_extra: and even more
>
> I don't use the EXPORT keyword at the beginning, I am not sure if it is
Hello,
are you looking for, e.g.,
#+latex_header: \addbibresource{bibliography.bib}
#+latex_header_extra: do some stuff
#+latex_header_extra: and even more
I don't use the EXPORT keyword at the beginning, I am not sure if it is needed.
Best,
Dominik
Alan Schmitt writes:
> Hello,
>
> I would
Hello,
I would like to have a multi-line export header when exporting a
subtree. I tried this:
:EXPORT_LATEX_HEADER: \makeatletter
:EXPORT_LATEX_HEADER+: \@setplength{refvpos}{\useplength{toaddrvpos}}
:EXPORT_LATEX_HEADER+: \makeatother
The problem is that it's exported on a single line, and as
13 matches
Mail list logo
