On Fri, Oct 23, 2015 at 8:27 AM, Éibhear <eibhear.geo@gmail.com> wrote:

> Matt Price <moptop99 <at> gmail.com> writes:
>
> >
> >
> >
> > On Thu, Sep 24, 2015 at 7:10 AM, Matt Price <moptop99 <at> gmail.com>
> wrote:
> >
> >
> > On Thu, Sep 24, 2015 at 12:00 AM, Nick Dokos <ndokos <at> gmail.com>
> wrote:
> > Matt Price <moptop99 <at> gmail.com> writes:
> >
> >
> >
> > -----
> >
> > it looks about right until the very end; Manually running "dot
> /tmp/babel-2749DTL/dot-2749Nkt -Tpng -o /home/matt/example-diagram.png"
> from
> a shell works fine. However, the result of:(org-babel-eval     (concat
> cmd         " " (org-babel-process-file-name in-file)         " "
> cmdline
>      " -o " (org-babel-process-file-name out-file)) "")
> >
> > is "nil".  Any idea why that might be?
> >
> >
> >
> > Just a quick addendum.  Pausing during debugging and running
> (with-temp-file in-file )(org-babel-eval  "dot
> /tmp/babel-2749DTL/dot-2749Nkt -Tpng -o /home/matt/example-diagram.png"
> "")
> >
> > from a scratch buffer also works.  So I am really confused -- maybe there
> is something wrong with ob-dot itself?
> >
> >
> >
> >
> > Again, many thanks,
> >
> > Matt
> >
> >
> >
> >
> >
> >
> >
>
> Hi Matt,
>
> Did you get this worked out?
>
> Thanks,
>
> Éibhear
>
>
hmm.  It looks like maybe I didn't -- I confess I'd forgotten about this
old email.  Looks like I just generated the diagram from a scratch buffer,
as described in my email.  Sorry I didn't get further!

Matt