From 4e84f496adb538db3d3fc75134d6e05086332bf9 Mon Sep 17 00:00:00 2001 From: Ralph Amissah Date: Sun, 27 Jun 2021 15:27:05 -0400 Subject: org-mode code block headers --- org/spine_markup_sample.org | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) (limited to 'org/spine_markup_sample.org') diff --git a/org/spine_markup_sample.org b/org/spine_markup_sample.org index 81a510a..92b057f 100644 --- a/org/spine_markup_sample.org +++ b/org/spine_markup_sample.org @@ -14,13 +14,15 @@ #+PROPERTY: header-args+ :results no #+PROPERTY: header-args+ :cache no #+PROPERTY: header-args+ :padline no +#+PROPERTY: header-args+ :mkdirp yes This is not how I would recommend preparing a markup document for spine. It is after all a text file with its own markup. However, as an experiment in developing on org-mode I prepare the document here. Its output is to be found in ../data/pod/sisu-spine-markup * spine markup sample ** pod.manifest -#+BEGIN_SRC text :tangle ../data/pod/sisu-spine-markup/pod.manifest +#+HEADER: :tangle ../data/pod/sisu-spine-markup/pod.manifest +#+BEGIN_SRC text doc: filename: sisu-spine-markup.sst language: en @@ -28,13 +30,15 @@ doc: ** conf/sisu_document_make -#+BEGIN_SRC text :tangle ../data/pod/sisu-spine-markup/conf/sisu_document_make +#+HEADER: :tangle ../data/pod/sisu-spine-markup/conf/sisu_document_make +#+BEGIN_SRC text #+END_SRC ** substantive document *** tangle -#+BEGIN_SRC text :tangle ../data/pod/sisu-spine-markup/media/text/en/sisu-spine-markup.sst +#+HEADER: :tangle ../data/pod/sisu-spine-markup/media/text/en/sisu-spine-markup.sst +#+BEGIN_SRC text <> <> <> -- cgit v1.2.3