From: Tom Short <tshort@epri.com>
To: emacs-orgmode@gnu.org
Subject: Re: [babel]: Some feedback after the first week usage
Date: Thu, 5 Nov 2009 22:48:03 +0000 (UTC) [thread overview]
Message-ID: <loom.20091105T234236-958@post.gmane.org> (raw)
In-Reply-To: 87639o287h.fsf@stats.ox.ac.uk
Dan Davison <davison <at> stats.ox.ac.uk> writes:
>
> Torsten Wagner <torsten.wagner <at> gmail.com> writes:
>
> <...>
> > 4. Is there a way to see all source code blocks of a single session tangled
> > together in a single buffer and changes in this buffer will be placed back
after
> > leaving into the individual blocks again
>
> It sounds nice, but very challenging. Would such a mechanism be robust
> to very disruptive edits in the tangled code buffer (e.g. moving large
> blocks of text around)? Would it be able to meaningfully maintain a
> mapping between buffer regions and code blocks? You'd want to start off
> by looking at the code in org-src.el to see whether you thought it could
> be extended.
One way this could be implemented is with an indirect buffer. In the indirect
buffer, you could use an overlay to hide all the org parts and just leave the
code parts visible. You're not really tangling, just hiding the non-code stuff.
You might even be able to operate the indirect buffer in ess-mode or python mode
if you wanted.
- Tom
next prev parent reply other threads:[~2009-11-05 22:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 8:27 [babel]: Some feedback after the first week usage Torsten Wagner
2009-11-05 15:57 ` Thomas S. Dye
2009-11-06 1:34 ` Torsten Wagner
2009-11-05 17:27 ` Dan Davison
2009-11-05 22:48 ` Tom Short [this message]
2009-11-06 18:56 ` Thomas S. Dye
2009-11-06 0:02 ` Eric Schulte
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=loom.20091105T234236-958@post.gmane.org \
--to=tshort@epri.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).