emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Karl Voit <mail@Karl-Voit.at>
To: Eric S Fraga <e.fraga@ucl.ac.uk>, emacs-orgmode@gnu.org
Cc: Rick Frankel <rick@rickster.com>
Subject: Re: process diagrams with dot and some glue using org
Date: Sun, 21 Jul 2013 21:05:11 +0200	[thread overview]
Message-ID: <2013-07-21T20-41-21@devnull.Karl-Voit.at> (raw)
In-Reply-To: <87vc46ea4y.fsf@ucl.ac.uk>

Eric S Fraga (e.fraga@ucl.ac.uk) wrote:

> Dear Karl,

Hi Eric,

> a couple of weeks ago you developed some code to convert a pair of
> tables to a graphviz digraph and you wrote a very useful Worg page about
> it:
> 
>   http://article.gmane.org/gmane.emacs.orgmode/74280
>   http://orgmode.org/worg/org-tutorials/org-dot-diagrams.html

Glad you enjoyed it!

> I have today had a real need for this so I copied the code and used
> it.  Worked like a charm!  Thanks for doing this.

You are very welcome!

> I just wanted to say two things about it:
> 
> 1. if the typical use case is to use the code with #+call:, it would be
>      more helpful to delete the #+header: line in the source code in the
>      Worg page. 

I have to admit, that I did not come up with the technical solution
which is described in the tutorial.  My part was the
requirement/idea and a very basic attempt. Rick Frankel[1]
contributed the LISP code and the final structure of the tables. As
a matter of fact, I had never used #+call before by myself. Rick was
also the author of the call statement[2] to re-use the code with
several tables.

>      This header line presumes that the particular tables in
>      your first example exist.  Deleting this line means that the code
>      can only be used via a #+call statement but I think this is more
>      logical.

I see your point.

However, in the tutorial, I wanted to start with a full example
using two tables and the ELISP block only.

In a second step, I wanted to re-use the ELISP block. You are right,
the #+header line is not necessary if the ELISP block is used by
#+src only. Are you suggesting, that there should be a remark on
this in the tutorial? If so, feel free to improve the text, if you
do have good ideas!

> 2. I appended a column to my node table with a description of each
>      node.  You've written your code so that it doesn't care if there
>      are extra columns.  This is a bonus!  My table not only provides
>      the data for the graph but also explains the graph to a reader.

Yes, I also do like this "feature" to add additional things.

Once again: I had the requirement of creating simple work-flows
within Org-mode, Rick was so kind and contributed the solution, and
I summarized the method in the tutorial.

So the "thank you" definitely belongs to Rick. Therefore, I added
him to the Cc.

Nice greetings from sunny Graz, Austria!

  1. http://article.gmane.org/gmane.emacs.orgmode/73854
  2. http://article.gmane.org/gmane.emacs.orgmode/73972
-- 
Karl Voit

  parent reply	other threads:[~2013-07-21 19:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-19 17:23 process diagrams with dot and some glue using org Eric S Fraga
2013-07-19 17:37 ` Rick Frankel
2013-07-19 17:56   ` Eric S Fraga
2013-07-20 11:02   ` Eric S Fraga
2013-07-20 12:47     ` Rick Frankel
2013-07-21 19:05 ` Karl Voit [this message]
2013-07-22  8:00   ` Eric S Fraga

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=2013-07-21T20-41-21@devnull.Karl-Voit.at \
    --to=mail@karl-voit.at \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=rick@rickster.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).