Thanks Eric, I didn't know that you could pass lisp code as header
arguments. It looks like it'll be best to conditionally tangle.
:tangle (if (string-match "myhost" system-name) "yes" "no")
Eric Schulte writes:
> Alan Lue writes:
>
>> Hi,
Hi, how does one tangle a single code block to multiple files?
I thought the following might work, but unfortunately it does not.
Set the frame size.
#+HEADERS: :tangle user-host-a.el user-host-b.el
#+BEGIN_SRC emacs-lisp
(setq initial-frame-alist '((width . 80) (height . 38)))
#+END_SRC
To p
Following up.
Does anyone else see this behavior? Headers always appear in the export
whenever my document includes a code block with a separate `#+HEADERS:'
line.
Alan Lue writes:
> I find that code block header arguments specified with `#+HEADERS:'
> consistently appear
I find that code block header arguments specified with `#+HEADERS:'
consistently appear in the exported document. For example, exporting the
following document to PDF or HTML will include the "exports" header in
the output:
* Manifestation of Problem
Look, our headers appear in the export:
#+
