Matt Huszagh writes:
>> Can you provide a patch against etc/ORG-NEWS announce this?
>
> Attached. Let me know what you think.
Applied (2af68d6a4) with a minor modification in the headline.
Thanks,
--
Bastien
Bastien writes:
> sorry for the delayed answer.
No worries!
> Can you provide a patch against etc/ORG-NEWS announce this?
Attached. Let me know what you think.
Matt
>From 51fb3ef9843ae45884803142f150c5d2f4f4d4c9 Mon Sep 17 00:00:00 2001
From: Matt Huszagh
Date: Sat, 24 Oct 2020 09:36:56 -07
Hi Matt,
sorry for the delayed answer.
Matt Huszagh writes:
> Bastien writes:
>
>> Prefer
>>
>> * lisp/ob-latex.el (org-babel-latex-preamble): New option for LaTeX
>> preamble customization.
>>
>> "New option" is quite standard, an "option" being a customizable
>> variable. In this case,
Bastien writes:
> Prefer
>
> * lisp/ob-latex.el (org-babel-latex-preamble): New option for LaTeX
> preamble customization.
>
> "New option" is quite standard, an "option" being a customizable
> variable. In this case, "New option" would probably be enough, given
> the name of the option is q
Hi Matt,
Matt Huszagh writes:
> Matt Huszagh writes:
>
>> I've added a few changes to the patch that additionally allow custom the
>> begin and end document environments. The purpose here is to allow latex
>> code within the document environment that is ignored by the body
>> export. For instan
Hi Matt,
Matt Huszagh writes:
> I've added a few changes to the patch that additionally allow custom the
> begin and end document environments. The purpose here is to allow latex
> code within the document environment that is ignored by the body
> export. For instance, I can set the page color w
Matt Huszagh writes:
> I've added a few changes to the patch that additionally allow custom the
> begin and end document environments. The purpose here is to allow latex
> code within the document environment that is ignored by the body
> export. For instance, I can set the page color with
> {\co
Matt Huszagh writes:
> Ok, I've finally gotten around to taking a crack at this. The patch is
> attached. Basically, it allows a lot more control when converting a
> latex source block into an svg image file.
I've added a few changes to the patch that additionally allow custom the
begin and end
Bastien writes:
> If you find the time to share your change as a _patch_ (not the whole
> updated Elisp function), that will allow more readers on this list to
> quickly understand what is at stake.
Ok, I've finally gotten around to taking a crack at this. The patch is
attached. Basically, it al
Hi Matt,
Matt Huszagh writes:
> What do people think? If there's any interest, I'm more than happy to
> put in the extra time and add this functionality to
> latex-execute.
If you find the time to share your change as a _patch_ (not the whole
updated Elisp function), that will allow more reader
I've thought about this more and the solution I presented above isn't
quite sufficient for me. I need something where I get complete control
over what goes in the latex source block on a block-by-block basis. In
other words, I don't want a user-configurable option like
org-format-latex-header plus
Ok, here's an implementation that seems to be working pretty well so
far.
`org-latex-img-process` is the new customization. Most of the execute
function is unaltered, but I've added the condition:
```
((and (not imagemagick)
(assoc extension org-latex-img-process))
I spent some time today trying to get latex babel source blocks to work
for me and discovered that calling `org-babel-execute:latex` ignores the
:headers header if the output file is a png without setting imagemagick
to t. It's easy to see this in the source code: the conditions mentioned
above lea
13 matches
Mail list logo
