From: "Thomas S. Dye" <tsd@tsdye.com>
To: Eric S Fraga <ucecesf@ucl.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: Business process diagrams in org-mode
Date: Tue, 16 Nov 2010 08:40:31 -1000 [thread overview]
Message-ID: <276A57E6-7BAD-46C5-B7F3-62D8A1088997@tsdye.com> (raw)
In-Reply-To: <87vd3x9nmp.fsf@ucl.ac.uk>
On Nov 16, 2010, at 6:35 AM, Eric S Fraga wrote:
> Bart Bunting <bart@bunting.net.au> writes:
>
>> Hi Eric,
>>
>> Thanks very much for the suggestion!
>>
>> I'm not familiar with dot but will invest some time to see if I can
>> get
>> my head around it.
>>
>> This sounds like a good solution. Perhaps just writing directly in
>> dot
>> will solve my problem.
>
> Possibly, although as it is possibly nicer to work with org tables,
> and
> because my train was delayed 45 minutes on the way to work this
> morning,
> here (attached as an org file with babel emacs lisp code) is one
> attempt
> at a solution.
>
> There is one bug in this code: for some reason, the dot code generated
> by the emacs lisp code gets embedded in an org EXAMPLE block. Not
> sure
> why but I have to do something else now... I'll try to come back to
> this later.
>
> Oh, I also changed your table so that each next step takes up a column
> entry in the table. This is not ideal but I didn't want to bother
> parsing the actual table entries.
>
> <businessprocess.org>
> HTH,
> eric
Hi Eric,
Neat! This gets rid of the #+begin_example ... #+end_example for me:
#+call: esf/business-process[:results value raw](table=processtable,
file="business.pdf", name="process") :results value raw
All the best,
Tom
next prev parent reply other threads:[~2010-11-16 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-14 1:59 Business process diagrams in org-mode Bart Bunting
2010-11-14 2:51 ` Thomas S. Dye
2010-11-14 3:09 ` John Hendy
2010-11-14 3:08 ` John Hendy
2010-11-15 11:25 ` Eric S Fraga
2010-11-15 19:16 ` Bart Bunting
2010-11-16 16:35 ` Eric S Fraga
2010-11-16 18:40 ` Thomas S. Dye [this message]
2010-11-16 19:16 ` 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=276A57E6-7BAD-46C5-B7F3-62D8A1088997@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=ucecesf@ucl.ac.uk \
/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).