emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: hugo@heagren.com
To: emacs-orgmode@gnu.org
Subject: Can :packages and :headers arguments in latex SRC blocks be made affect EXPORT blocks of results?
Date: Tue, 08 Nov 2022 23:04:22 +0000	[thread overview]
Message-ID: <c975ac5b3923b0c25d5bb7c3cc330acd@heagren.com> (raw)

tl;dr: can I have `:packages' and `:headers' arguments from LaTeX src
block take effect, when I export those blocks as export blocks?

I wanted a way to write tikz snippets inside org documents, preview them
in the document as images, but have the tikz /code/ appear when I
exported to LaTeX. So far I have this:

| #+header: :results (if (org-export-derived-backend-p 
org-export-current-backend 'latex) "latex" "file raw")
| #+header: :file (if (org-export-derived-backend-p 
org-export-current-backend 'latex) nil "foo.png")
| #+header: :packages '((nil "tikz" t))
| #+header: :imagemagick t :fit t
| #+header: :headers '("\\usetikzlibrary{calc,positioning,patterns}")
| #+begin_src latex
| \begin{tikzpicture}[on grid,
|   font=\footnotesize,
|   level distance=2.5cm,
|   sibling distance=2.5cm,
|   every node/.style={circle,draw,fill=white},
|   touch/.style={circle,draw=red!100,fill=red!40,thick},
|   invirtueof/.style={circle,draw=red!50,fill=red!20,very thick}]
|   \node [invirtueof] {Car}
|   child {node {wheel}}
|   child {node [invirtueof] {body}
|     child {node {driver door}}
|     child {node [invirtueof] {passenger door}
|       child {node [touch] {region of door}}}};
| \end{tikzpicture}

This works almost perfectly. It's set generate an EXPORT block of LaTeX
code when exporting, and an inline image in the results block otherwise.
When generating this inline image, it takes into account the necessary
`:packages' and extra `:headers' defined.

The only problem is that when I export to LaTeX, what is included is
/just/ what was in the results block, which is /just/ the code inside
the original src block (i.e. the export does not include the `:packages'
or `:headers' information, and thus fails to compile because the LaTeX
file doesn't load tikz).

Is there a way around this? Either to export the src block another way,
or to add metadata to the to the resulting EXPORT block (or just text,
though I'm not sure how that would work for `:packages', since they
require text to be added to the resulting exported LaTeX file in a
different place from where the text of the block goes).

Ideally, I would like to not have to change anything in the file between
working on it (previewing) and exporting. Solutions to similar problems
(e.g. <https://emacs.stackexchange.com/a/60714/34394>) seem to require
commenting and uncommenting lines. I would really like a single,
write-once solution (and am perfectly happy with it being verbose).

If there /isn't/ a way to do this at the moment but someone knows
roughly what would have to change in org for there to be, that would be
great information to have too. I would be happy to try to work up a
patch. I've looked at some of the code and it looks just about



             reply	other threads:[~2022-11-08 23:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 23:04 hugo [this message]
2022-11-09  4:53 ` Can :packages and :headers arguments in latex SRC blocks be made affect EXPORT blocks of results? Ihor Radchenko
2022-11-09 17:30 ` Juan Manuel Macías

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c975ac5b3923b0c25d5bb7c3cc330acd@heagren.com \
    --to=hugo@heagren.com \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).