From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [Babel] detangle
Date: Fri, 29 Oct 2010 15:32:01 +0100 [thread overview]
Message-ID: <87wrp16pem.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87ocadv2ib.fsf@gmail.com> (Eric Schulte's message of "Fri, 29 Oct 2010 02:15:08 -0600")
"Eric Schulte" <schulte.eric@gmail.com> writes:
> Hi,
>
> I've just added functions for detangling code from pure source code
> files back into code blocks in the org-mode files from whence they were
> tangled.
Wow. It just gets better all the time!! :-)
> This is done by the new `org-babel-detangle' function.
> Additionally the new `org-babel-tangle-jump-to-org' function can be used
> to navigate from a pure source code file back to the related code block
> in the original Org-mode file.
>
> Both of these new functions require that the code block was tangled with
> comments which can be accomplished by setting the :comments header to
> "yes".
I've tried the first couple of steps: added the comments header and
tangled my code, ledger in this case. I've had a looked at the tangled
code and I get lines such as this one inserted:
: ; [[id:8fe917c4-257f-45f7-839b-68b5772e5443][%sourcename]]
Obviously, =%sourcename= should have been replaced by something in the
tangling operation as, subsequently, the jump command doesn't work. I
assume that the detangling won't work either.
Is there something I (or you?) should add to =ob-ledger.el= perhaps?
I've not tried any other codes as I don't /tangle/ often.
Thanks,
eric
--
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29 570D C891 93D8 FFFC F67D
next prev parent reply other threads:[~2010-10-29 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 8:15 [Babel] detangle Eric Schulte
2010-10-29 14:32 ` Eric S Fraga [this message]
2010-10-29 15:01 ` Eric Schulte
2010-10-29 15:36 ` Eric S Fraga
2010-11-04 13:53 ` Eric Schulte
2010-11-04 16:01 ` Eric S Fraga
2010-10-31 16:56 ` David Maus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wrp16pem.fsf@ucl.ac.uk \
--to=ucecesf@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.