On Mon, Apr 11, 2022 at 10:53 PM Vikas Rawal wrote:
>
> For a major project like this, I would just put these in a separate file, and
> include it using #+INCLUDE:
Org has a special keyword for the purpose of including *just the setup
stuff*: #+setupfile
See (org) Export Settings.
#+include
Hi William,
William Denton writes:
> What sorts of practices do people have for managing lots of LaTeX
> headers? Juan Manuel Macías, you mentioned something like
> this---literate programming in Org to export LaTeX source---may I ask
> how you do it?
When it comes to a large project, for
Hi William,
> I have another question related to managing a book I’m doing building for
> export
> to LaTeX: what do people do for managing all of the headers?
Generally, I don’t like thinking about what LaTeX headers I need. That’s why I
developed
William Denton writes:
> I have another question related to managing a book I'm doing building for
> export to LaTeX:
> what do people do for managing all of the headers?
>
I only use the #+latex_headers or #+latext-headers-extra lines for 'one
off' type documents. If I'm going to be writing
For a major project like this, I would just put these in a separate file,
and include it using #+INCLUDE:
Vikas
On Tue, 12 Apr 2022 at 06:37, William Denton wrote:
> I have another question related to managing a book I'm doing building for
> export
> to LaTeX: what do people do for managing
I have another question related to managing a book I'm doing building for export
to LaTeX: what do people do for managing all of the headers?
I have about 30 #+latex_header lines in the project I'm working on, and I'm
still just working on it as a basic article. When I'm ready to do more
