From: Dmitri Makarov <dmakarv@gmail.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: graphviz dot block export and evaluate
Date: Fri, 28 Sep 2012 19:27:59 +0200 [thread overview]
Message-ID: <821644A1-7764-401C-858A-3ED9FF60629F@gmail.com> (raw)
In-Reply-To: <m1k3vekr2w.fsf@tsdye.com>
Hi Tom and Bastien,
Thank you, your answers helped a lot.
My fault that I used "export" not "exports" and that I didn't read the section Specific header arguments in the Org manual.
Thanks!
Dmitri
On Sep 28, 2012, at 7:14 PM, tsd@tsdye.com (Thomas S. Dye) wrote:
> Dmitri Makarov <dmakarv@gmail.com> writes:
>
>> Hi all,
>>
>> Has anyone successfully exported and evaluated src blocks with
>> graphviz dot code?
>> I'm trying to export this block
>>
>> #+BEGIN_SRC dot :export both
>> digraph G {
>> A -> B
>> }
>> #+END_SRC
>>
>> and I'm getting the error
>>
>> org-babel-exp processing...
>> executing Dot code block...
>> file-name-extension: Wrong type argument: stringp, nil
>>
>> How do you debug such problems?
>>
>> Regards,
>>
>> Dmitri
>
> Aloha Dmitri,
>
> Currently, you can debug such problems by looking at the source code of
> ob-dot.el. Or, by asking the list, as you did.
>
> Your example is lacking a :file header argument. dot source code blocks
> produce graphics files and babel leaves it to the user to name the
> output file. The file-name-extension function is looking for the value
> of the :file header argument, so that it can configure the call to dot.
> It is expecting to see a string, but gets nil because the header
> argument is absent.
>
> Also, the correct keyword is :exports, with a final "s".
>
> You can find an example of dot code use here:
> http://www.jstatsoft.org/v46/i03
>
> hth,
> Tom
> --
> Thomas S. Dye
> http://www.tsdye.com
prev parent reply other threads:[~2012-09-28 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 16:51 graphviz dot block export and evaluate Dmitri Makarov
2012-09-28 17:07 ` Bastien
2012-09-28 17:14 ` Thomas S. Dye
2012-09-28 17:27 ` Dmitri Makarov [this message]
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=821644A1-7764-401C-858A-3ED9FF60629F@gmail.com \
--to=dmakarv@gmail.com \
--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).