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: Wed, 11 Apr 2012 10:08:51 -0400	[thread overview]
Message-ID: <87vcl62wek.fsf@gmx.com> (raw)
In-Reply-To: <CAPaq-gMr0EMamsas4kATqzNWi9tz9ZDJDwCqQhQU2nDbu20iKg@mail.gmail.com> (Torsten Wagner's message of "Wed, 11 Apr 2012 23:45:54 +0900")

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.

Best,

Torsten Wagner <torsten.wagner@gmail.com> writes:

> Hi,
>
> I guess we had such a discussion some time ago already.
> I just started again to use inline source code blocks
>
> e.g.
>
> text text text src_python[:session]{print((U[0]-U[1])*1000)} mV text text text
>
> if you have a lot of these in a text its rather hard to read.
> I was thinking of something similar like links in org-mode
> The inline source code gets hidden behind the result of the last
> evaluation and can be accessed in the same way like links in org-mode.
> It could even open up in a buffer of the target language like source
> code blocks.
> The above example would be reduced to
>
> text text text _355_ mV text text text
>
> C-c C-c would update the result
> mouse click open the source code in a language specific buffer
> etc.
>
> This would really make it more readable
>
> All the best
> Torsten
>

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

  reply	other threads:[~2012-04-11 16:09 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 [this message]
2012-04-26  8:37   ` Eric Fraga
2012-04-26 13:08     ` Eric Schulte
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=87vcl62wek.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).