emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <eric.schulte@gmx.com>
To: Torsten Wagner <torsten.wagner@gmail.com>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: [babel] hide inline source code blocks by results
Date: Thu, 26 Apr 2012 09:08:21 -0400	[thread overview]
Message-ID: <878vhiabei.fsf@gmx.com> (raw)
In-Reply-To: <87zk9ylwhy.fsf@ucl.ac.uk> (Eric Fraga's message of "Thu, 26 Apr 2012 18:07:13 +0930")

Eric Fraga <e.fraga@ucl.ac.uk> writes:

> Eric Schulte <eric.schulte@gmx.com> writes:
>
>> Currently inline blocks like don't associate themselves with their
>> results, they are only expected to be evaluated on export, so the
>> functionality you suggest below would require first changing how results
>> are associated with inline code blocks.
>>
>> Another option would be to hide everything but the body of the block,
>> but this may be more confusing than it is worth.
>
> Eric,
>
> I do like what Torsten suggested a lot.  I wonder if a halfway solution
> would be possible.  Define a babel: link type which includes the src_xxx
> code and let the description part of the link be whatever the author
> wants it to be.  I wouldn't mind not knowing the result of the code
> execution as I don't know that at the moment anyway.
>
> So, something like this would be nice:
>
> ... and the result is [[babel:src_octave{3*x+5}][f(x)]] which
> demonstrates ...
>
> which would look like
>
> ... and the result is f(x) which demonstrates ...
>
> (with f(x) highlighted as a link).
>
> Could something like this be possible?
>
> And, to take this further, could the highlighting differ depending on
> link type?  I've not explored this latter aspect so maybe it's already
> possible...
>

I think both this and Torsten's original idea would both be nice
options.  Preferably the final solution would subsume either use case.
Unfortunately either implementation would require a fairly significant
amount of work on the inline source block system, work which I
unfortunately do not have time for at the moment (although I'm happy to
help if anyone else wants to jump into the code).

Thanks,

>
> thanks,
> eric

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/

  reply	other threads:[~2012-04-26 15:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 14:45 [babel] hide inline source code blocks by results Torsten Wagner
2012-04-11 14:08 ` Eric Schulte
2012-04-26  8:37   ` Eric Fraga
2012-04-26 13:08     ` Eric Schulte [this message]
2012-04-27 13:25       ` Eric 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=878vhiabei.fsf@gmx.com \
    --to=eric.schulte@gmx.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=torsten.wagner@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).