From: "Eric Schulte" <schulte.eric@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-exp-block patch and Graphviz Demo
Date: Wed, 10 Jun 2009 09:06:09 -0700 [thread overview]
Message-ID: <m2zlcg6pla.fsf@gmail.com> (raw)
In-Reply-To: <20090610152940.GA11193@thinkpad.adamsinfoserv.com> (Russell Adams's message of "Wed, 10 Jun 2009 10:29:40 -0500")
Russell Adams <RLAdams@AdamsInfoServ.Com> writes:
>> Since you would rather go to EPS as an intermediary step, then I would
>> recommend defining a new block type which can handle this two-stage
>> process. There are instructions in org-exp-blocks.el, and I would
>> recommend using `org-export-blocks-format-dot' in
>> contrib/lisp/org-exp-blocks.el as your starting point. It should be
>> possible to achieve the result your want with only one or two lines of
>> new elisp probably inserted right after the following line
>>
>> (shell-command (concat "dot " data-file " " args " -o " out-file))
>>
>> Cheers -- Eric
>
> I'm still just teething in lisp, but I'll give it a peek.
>
This *should* be a good gentle introduction to lisp programming, and
probably shouldn't include much more than the introduction of another
call to `shell-command' which calls eps on the out-file.
If you run into problems feel free to email me off list, and I'd be
happy to try to share pointers.
>
> Have you compared the output between dot going straight to pdf, vs dot
> to eps to pdf?
>
> Attached are a pair of pdf's for comparison. The default font in eps
> is better, and the line style is blunted and looks better vs the
> arrows showing up going through the nodes.
I see what you mean, subtle but definitely looks nicer through EPS.
>
> Perhaps I can control these in the dot file, I'll look into it.
>
Really it would probably be much easier to do this with a new block
type... what do the commands look like when you do this by hand?
Cheers -- Eric
>
> Thanks.
>
>
> ------------------------------------------------------------------
> Russell Adams RLAdams@AdamsInfoServ.com
>
> PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/
>
> Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2009-06-10 16:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 19:09 org-exp-block patch and Graphviz Demo Russell Adams
2009-05-28 7:48 ` Carsten Dominik
2009-05-28 13:44 ` Eric Schulte
2009-05-28 14:23 ` Eric Schulte
2009-05-28 18:03 ` Org Mode List
2009-05-28 22:47 ` Russell Adams
2009-05-28 22:57 ` Eric Schulte
2009-06-09 15:50 ` Russell Adams
2009-06-10 14:51 ` Eric Schulte
2009-06-10 15:29 ` Russell Adams
2009-06-10 16:06 ` Eric Schulte [this message]
2009-06-10 16:22 ` Russell Adams
2009-06-10 17:12 ` Eric Schulte
2009-06-10 17:54 ` Mark Elston
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=m2zlcg6pla.fsf@gmail.com \
--to=schulte.eric@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).