-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/07/2010 19:22, Eric Schulte wrote:
Hi Rainer,
Dr Rainer M Krug r.m.k...@gmail.com writes:
On 13/07/2010 02:46, Eric Schulte wrote:
Hi Rainer,
With the tangling comments generated by the latest Org-mode, the
following function should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Eric,
On Mon, Jul 12, 2010 at 8:04 PM, Eric Schulte schulte.e...@gmail.comwrote:
Hi Rainer,
If I'm understand you correctly you want the absolute position (by LOC)
of the lines of R code to be the same in both the original org file and
the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/07/2010 02:46, Eric Schulte wrote:
Hi Rainer,
With the tangling comments generated by the latest Org-mode, the
following function should be able to jump from any code in a tangled
code file back to the relevant block in the original
Hi Rainer,
Dr Rainer M Krug r.m.k...@gmail.com writes:
On 13/07/2010 02:46, Eric Schulte wrote:
Hi Rainer,
With the tangling comments generated by the latest Org-mode, the
following function should be able to jump from any code in a tangled
code file back to the relevant block in the
Hi Rainer,
If I'm understand you correctly you want the absolute position (by LOC)
of the lines of R code to be the same in both the original org file and
the tangled file or R code. I don't think this is possible. It is
possible to tangle code blocks in any order (not just the order in which
Hi Rainer,
With the tangling comments generated by the latest Org-mode, the
following function should be able to jump from any code in a tangled
code file back to the relevant block in the original Org-mode file.
--8---cut here---start-8---
(defun
