From: Fabrice Niessen <fni-news-TA4HMoP+1wHrZ44/DZwexQ@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Tangling src blocks to files as part of export
Date: Thu, 13 Nov 2014 17:56:50 +0100 [thread overview]
Message-ID: <86tx23avjh.fsf@example.com> (raw)
In-Reply-To: 871A2C12-586B-4E42-AEE9-31BFAA4C8EBF@gmail.com
Hello Michael,
Michael Weylandt wrote:
>> On Nov 13, 2014, at 10:54 AM, Michael Weylandt <michael.weylandt-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>>
>> Is it possible to have certain blocks tangled as part of export so
>> that they are available as input files to later source blocks?
>>
>> E.g.,
>>
>> #+BEGIN_SRC python :tangle hello.py
>> print "Hello World"
>> #+END_SRC
>>
>> #+BEGIN_SRC sh
>> python hello.py
>> #+END_SRC
>>
>> If I tangle before running, then the second code block will work;
>> else, it fails because 'hello.py' is not found. [1]
>>
>> I can run tangle and export in a row (and I have my own function to
>> do just that) but is there a native org way to do so?
>
> Adding org-babel-tangle to the org-export-before-processing-hook does
> the job, but I'd still be interested in knowing if there's a more
> official method.
For such a work, I'm using this home-made function:
--8<---------------cut here---------------start------------->8---
(with-eval-after-load "org"
(defun org-save-buffer-and-do-related ()
"Save buffer, execute/tangle code blocks, and export to HTML/PDF."
(interactive)
(let* ((orgfile (buffer-file-name))
(base-name (file-name-base orgfile))
(htmlfile (concat base-name ".html"))
(pdffile (concat base-name ".pdf")))
(save-buffer) ; See other commands in
; `before-save-hook':
; `org-update-all-dblocks'
; `org-table-iterate-buffer-tables'.
(when (derived-mode-p 'org-mode)
;; (org-babel-execute-buffer) ; XXX Why should we execute all code blocks?
(let ((before-save-hook nil))
(save-buffer))
(org-babel-tangle)
(when (file-exists-p htmlfile)
(if (file-newer-than-file-p orgfile htmlfile)
(org-html-export-to-html)
(message "HTML is up to date with Org file")))
(when (file-exists-p pdffile)
(if (file-newer-than-file-p orgfile pdffile)
(if (string-match "^#\\+BEAMER_THEME: " (buffer-string))
(org-beamer-export-to-pdf)
(org-latex-export-to-pdf))
(message "PDF is up to date with Org file")))
(beep))))
(define-key org-mode-map (kbd "<f9>") 'org-save-buffer-and-do-related))
--8<---------------cut here---------------end--------------->8---
Best regards,
Fabrice
--
Fabrice Niessen
Leuven, Belgium
http://www.pirilampo.org/
next prev parent reply other threads:[~2014-11-13 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 15:54 Tangling src blocks to files as part of export Michael Weylandt
2014-11-13 16:15 ` Michael Weylandt
2014-11-13 16:56 ` Fabrice Niessen [this message]
2014-11-14 8:39 ` Rainer M Krug
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=86tx23avjh.fsf@example.com \
--to=fni-news-ta4hmop+1whrz44/dzwexq@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).