emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Gunnar Wolf <gwolf@gwolf.org>
To: emacs-orgmode@gnu.org
Subject: Babel-generated files not part of published projects?
Date: Wed, 30 Jan 2013 12:00:31 -0600	[thread overview]
Message-ID: <20130130180031.GA44277@gwolf.org> (raw)

Hi,

I have the following (partial) target as a publishing declaration:

(setq org-publish-project-alist
      '(("notas-html"
         :base-directory "~/vcs/sistemas_operativos/notas/"
         :base-extension "org"
         :publishing-directory "~/vcs/sistemas_operativos/html"
         :recursive t
         :publishing-function org-publish-org-to-html
         :headline-levels 4
         :timestamp nil
         :creator-info nil
         :todo-keywords nil
         :html-preamble ""
         :html-postamble ""
         :auto-preamble t
	 )
	("notas-pdf"
	 :base-directory "~/vcs/sistemas_operativos/notas/"
	 :base-extension "org"
	 :publishing-directory "~/vcs/sistemas_operativos/pdf"
	 :recursive t
	 :publishing-function org-publish-org-to-pdf
	 :headline-levels 4
	 :auto-preamble t
	 )
 (...)
        ))

And I have several Dot-generated snippets as part of my text, such as
this one:

#+begin_src dot :file ltxpng/estados_proceso.png
digraph G {
        layout = dot;
        node [shape = box];
	(...)
}
#+end_src

When I export a single file (i.e. with C-c C-e p), the file gets
generated with the specified filename and included in the resulting
PDF. However, when I do it via org-publish-all (or
org-publish-project), the code does not get executed, and the
resulting files are missing the diagramas.

What am I missing?

Thanks,

             reply	other threads:[~2013-01-30 18:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-30 18:00 Gunnar Wolf [this message]
2013-01-31 13:42 ` Babel-generated files not part of published projects? Bastien
2013-01-31 14:01   ` Gunnar Wolf

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=20130130180031.GA44277@gwolf.org \
    --to=gwolf@gwolf.org \
    --cc=emacs-orgmode@gnu.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).