From: Seth Burleigh <wburle4@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>, emacs-orgmode@gnu.org
Subject: Re: Re: [babel] Painless integration of source blocks with language
Date: Mon, 24 Jan 2011 08:49:24 -0600 [thread overview]
Message-ID: <AANLkTikFVXvEsfXof7DoGpBHmncFGAXcJ2rG4N=FRxHa@mail.gmail.com> (raw)
In-Reply-To: <87oc7dic8k.fsf@gmail.com>
> You are correct, while the tangling works, the detangling still needs to
> be updated to take into account the fact that there may now be nested
> sections of tangled code -- which it doesn't currently. Hopefully this
> wont be too large of a code change...
>
It probably wouldnt involve much code change, since there is very few
functions which operate on tangled files - detangle and jump to source
block?
It would be a good time to implement some functions, maybe like this,
which did operate on tangled files -
org-babel-detangle-src-block-info
which, given a point on the line of a link, would produced something like
((end . '(0 100)) (middle . (10 90)) (children . (((end . (20 30))
...) ... more children))
where end is the position in the buffer from the beginning of the link
to the end of the matching end link, and middle is the body portion.
. Then define a function which maps over
all of the detangled toplevel src blocks of a file(like what is done
for tangled src blocks).
And then one could call org-babel-detangle-src-block which would do
some recursive detangling
if has children, detangle children
get body string
replace the children in body string (using end) with appropriate noweb syntax
replace appropriate org block with code
and then you could call org-babel-detangle which would detangle all of
a file, using the map function mentioned previously to collect all
source blocks.
(with-error
detangle all toplevel blocks of file
)
where with-error will catch any errors, replace org file with original
content if an error is thrown, and then reraise the error.
next prev parent reply other threads:[~2011-01-24 14:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 22:29 [babel] Painless integration of source blocks with language Seth Burleigh
2011-01-09 1:54 ` Eric Schulte
2011-01-09 9:40 ` Štěpán Němec
2011-01-09 17:59 ` Eric Schulte
2011-01-10 0:59 ` Seth Burleigh
2011-01-10 2:13 ` Eric Schulte
2011-01-10 3:49 ` Seth Burleigh
2011-01-10 4:01 ` Seth Burleigh
2011-01-11 17:00 ` Eric Schulte
2011-01-10 18:46 ` Eric S Fraga
2011-01-11 17:12 ` Eric Schulte
[not found] ` <AANLkTi=dNTn6HBeR4wV7039FDDyPGtmWbmL0biFwT-ta@mail.gmail.com>
2011-01-11 23:09 ` Seth Burleigh
2011-01-13 9:11 ` Eric S Fraga
2011-01-13 15:23 ` Seth Burleigh
2011-01-13 21:23 ` Eric Schulte
2011-01-13 23:44 ` Seth Burleigh
2011-01-16 15:31 ` Eric Schulte
2011-01-17 9:29 ` Sébastien Vauban
2011-01-17 16:18 ` Eric Schulte
2011-01-17 19:32 ` Sébastien Vauban
2011-01-17 22:15 ` Seth Burleigh
2011-01-17 22:44 ` Sébastien Vauban
2011-01-18 18:11 ` Seth Burleigh
2011-01-18 18:14 ` Seth Burleigh
2011-01-18 18:38 ` Seth Burleigh
2011-01-19 7:28 ` Eric Schulte
2011-01-24 14:49 ` Seth Burleigh [this message]
2011-01-18 19:53 ` Bastien
2011-01-24 11:56 ` Dan Davison
2011-01-24 18:56 ` Eric S Fraga
2011-01-26 10:43 ` Sébastien Vauban
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='AANLkTikFVXvEsfXof7DoGpBHmncFGAXcJ2rG4N=FRxHa@mail.gmail.com' \
--to=wburle4@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.com \
--cc=wxhgmqzgwmuf@spammotel.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).