From: Carsten Dominik <carsten.dominik@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-exp-blocks: what about previewing blocks ?
Date: Fri, 26 Jun 2009 06:17:51 +0200 [thread overview]
Message-ID: <08136B46-C923-4540-90E1-BD5850745F80@gmail.com> (raw)
In-Reply-To: <m2skhnyfmr.fsf@gmail.com>
On Jun 26, 2009, at 2:59 AM, Eric Schulte wrote:
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> On Jun 18, 2009, at 11:32 AM, Nicolas Girard wrote:
>>
>>> 2009/6/18 Carsten Dominik <carsten.dominik@gmail.com>
>>>
>>> On Jun 17, 2009, at 2:40 AM, Nicolas Girard wrote:
>>>
>>> Hi all,
>>>
>>> currently the code in org-exp-blocks is intended for pre-processing
>>> only.
>>> It seems to me like org-mode would gain a very powerful feature, if
>>> blocks could also be previewed in their own buffer, using the same
>>> mechanism as the org-format-latex function.
>>> What do you think ?
>>>
>>> I don't see how this could be done in a general way. I guess you
>>> mean in particular
>>> the graphics blocks like ditaa?
>>>
>>> Yes. For any block type bt, if it makes sense, it would be possible
>>> to write such org-block-<bt>-generate-image(body) that takes the
>>> block as argument and returns the path of the image it produced.
>>>
>>> Then:
>>> - for exporting: the existing org-export-blocks-format-<bt>
>>> functions would simply call their respective
>>> org-block-<bt>-generate-
>>> image and work the same ;
>>> - for previewing a block of type <bt>: if such org-block-<bt>-
>>> generate-image exists, call it and display it the same way org-
>>> format-latex does
>>>
>>> Wouldn't it be great ?
>>
>> Yes, it would be. First you will need to talk Eric Schulte into
>> splitting the image generation functions into separate functions.
>> The I could look into the preview functionality.
>>
>
> I recently sent out an email announcement of development on org-babel
> which should provide a unified backend for evaluating source-code
> contained in org-mode blocks. If org-exp-blocks is using org-babel
> for
> it's source-code evaluation the ability to interactively evaluate
> blocks
> will come for free. This would be my preference rather than
> implementing a new code-evaluation schema for org-exp-blocks.
>
> I suppose that this would assume that org-babel is accepted into the
> core of org-mode (for it to be a requirement of org-exp-blocks which
> is
> now part of the org-mode core). While this would be my preference, it
> is certainly not my decision to make, and I honestly haven't given it
> much thought up until this point.
From your post yesterday, without looking closer at org-babel,
it sounded to me that it is still under heavy development,
so maybe it is too early for the core at this moment?
No principal objections, of course.
- Carsten
next prev parent reply other threads:[~2009-06-26 4:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 0:40 org-exp-blocks: what about previewing blocks ? Nicolas Girard
2009-06-18 7:41 ` Carsten Dominik
2009-06-18 9:32 ` Nicolas Girard
2009-06-19 15:31 ` Carsten Dominik
2009-06-26 0:59 ` Eric Schulte
2009-06-26 4:17 ` Carsten Dominik [this message]
2009-06-26 17:16 ` Eric Schulte
2009-08-27 16:38 ` Carsten Dominik
2009-08-27 18:51 ` Eric Schulte
2009-08-28 8:02 ` Carsten Dominik
2009-08-28 16:06 ` Eric Schulte
2009-08-28 16:31 ` Bernt Hansen
2009-06-18 8:21 ` Carsten Dominik
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=08136B46-C923-4540-90E1-BD5850745F80@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.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).