From: "Eric Schulte" <schulte.eric@gmail.com>
To: maurizio.vitale@polymath-solutions.com
Cc: emacs-orgmode@gnu.org
Subject: [babel] Re: Re: [org-babel] Idea: Rendering output of code blocks inline (like org links)
Date: Fri, 16 Oct 2009 08:34:13 -0600 [thread overview]
Message-ID: <m2eip3z9ui.fsf_-_@gmail.com> (raw)
In-Reply-To: <87zl7sknrv.fsf@cuma.i-did-not-set--mail-host-address--so-tickle-me> (Maurizio Vitale's message of "Thu, 15 Oct 2009 23:42:28 -0400")
Maurizio Vitale
<mav@cuma.i-did-not-set--mail-host-address--so-tickle-me> writes:
>>>>>> "Eric" == Eric Schulte <schulte.eric@gmail.com> writes:
>
> Eric> 3) the results of a source code block are in no way
> Eric> constrained to be located after the body of the block. In
> Eric> cases where they are not located near each other the body
> Eric> would be invisible (which is not desirable) and when viewing
> Eric> the results there would be no way to tell if there is or isn't
> Eric> a source-block hidden beneath it
>
> For this to be useful for what the OP wanted to achieve it should be
> possible to ask for re-evaluation when on the result block.
>
the only tricky part of this would be capturing C-c C-c when on results,
as this key binding already has a well defined meaning in most results
types (for example in tables). However if we are willing to introduce a
new keybinding the actual function would be relatively simple given the
helper functions mentioned below.
>
> Also, it would be nice to be able to switch easily between source and
> result blocks (maybe this is possible, haven't checked).
>
there are currently functions which return the location of a results
block when called from a source block, and vice versa.
(org-babel-where-is-src-block-result &optional INSERT)
(org-babel-find-named-block name)
The only issue in exposing these to the user is the possibility of
polluting the already very dense space of Org-mode keybindings.
>
> Maybe with this additional functionality one can get most of the
> hiding-the-source functionality and put all the source blocks in the
> final page of the document.
>
Ah, I think I understand. That would be a much simpler path towards
achieving much of the "hiding" functionality originally proposed. I
will add this discussion in a PROPOSED state to the Org-babel task list.
Thanks -- Eric
>
> The only difference I see is that when switching to the source block you
> loose the visual context around it.
>
> Regards,
>
> Maurizio
>
>
>
> _______________________________________________
> 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
prev parent reply other threads:[~2009-10-16 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 15:08 [org-babel] Idea: Rendering output of code blocks inline (like org links) Marcelo de Moraes Serpa
2009-10-15 22:42 ` Eric Schulte
2009-10-16 3:42 ` Maurizio Vitale
2009-10-16 14:34 ` Eric Schulte [this message]
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=m2eip3z9ui.fsf_-_@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=maurizio.vitale@polymath-solutions.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).