On Mon, Apr 11, 2022 at 10:57 AM Max Nikulin wrote:
> There are a some problems with info links outside of Emacs:
> - Export to PDF
Yeah, I recently realized that I will need to add custom support for
exporting info: links using ox-hugo. I made a small blog post out of
this learning:
Hanspeter Gisler writes:
> OBSERVED BEHAVIOR
> =
>
> The following 2 files 'correct_face_rendering.org' and
> 'incorrect_face_rendering.org' render the 3rd headings timestamp face
> differently, once correctly and once incorrectly.
>
> incorrect_face_rendering.org
>
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
