From: Eric Schulte <schulte.eric@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>,
Org-mode <emacs-orgmode@gnu.org>
Subject: Re: babel work flow
Date: Fri, 15 Jul 2011 09:36:55 -0600 [thread overview]
Message-ID: <87mxgfk10q.fsf@gmail.com> (raw)
In-Reply-To: m1k4bkamf2.fsf@tsdye.com
tsd@tsdye.com (Thomas S. Dye) writes:
> "Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com> writes:
>
>> Hi Thomas,
>>
>> Thomas S. Dye wrote:
>>> I want to use one of the dot utilities, tred, in a way that preserves my
>>> ability to distribute the Org-mode file as reproducible research, i.e.,
>>> intermediate results should end up in the Org-mode file or be passed
>>> along in a chain.
>>>
>>> Right now I have a python routine that reads a couple of Org-mode tables
>>> and outputs a valid dot graph. I'm saving this to a file, dot-temp.gv,
>>> and then running some shell commands, like this:
>>>
>>> #+begin_src sh
>>> tred dot-temp.gv > test.gv
>>> dot -o test.pdf -Tpdf test.gv
>>> open test.pdf
>>> #+end_src
>>>
>>> The graph is just what I want, but I can't see how to automate the
>>> process in Org-mode. In particular, the tred step trips me up. Do I
>>> have to make babel, tred-aware?
>>
>> Sorry if I misunderstand, but could you be more explicit (for me) on what the
>> problem is? Why is it a problem for you to have that sh block inside your
>> Org. It is executed automagically upon exporting, no? If yes, why is that not
>> good enough?
>>
>> Best regards,
>> Seb
>
> Aloha Seb,
>
> Yes, babel is working fine and the sh block does its job.
>
> The problem is that I like to see intermediate results in the Org-mode
> file and the sh block works instead with files that reside outside Org-mode.
>
> In this particular case, I'd prefer to have dot-temp.gv in a results
> block in the Org-mode file, and then pass this results block into a
> source code block where tred can manipulate it, and which returns its
> results to the Org-mode file.
>
> That way, the skeptical inquirer need only consult the Org-mode file to
> be convinced that tred removed the transitive relations from the
> digraph. It would be an easy matter to compare the two results blocks.
>
> All the best,
> Tom
Hi Tom,
Maybe rather than saving the output of your python block to an external
file you could save it into the Org-mode file, into a results block
named e.g., "dot-temp", and then you could do the following in your sh
code block...
#+begin_src sh :var body=dot-temp
echo $dot-temp > dot-temp.gv
tred dot-temp.gv > test.gv
dot -o test.pdf -Tpdf test.gv
rm dot-temp.gv
open test.pdf
#+end_src
Hope this helps -- Eric
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2011-07-15 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 23:09 babel work flow Thomas S. Dye
2011-07-14 7:34 ` Sebastien Vauban
2011-07-14 15:53 ` Thomas S. Dye
2011-07-15 15:36 ` Eric Schulte [this message]
2011-07-15 16:58 ` Thomas S. Dye
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=87mxgfk10q.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.com \
--cc=wxhgmqzgwmuf@spammotel.com \
/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).