From: Eric Schulte <schulte.eric@gmail.com>
To: Rainer M Krug <Rainer@krugs.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: refine org-babel-tangle-jump-to-org?
Date: Thu, 06 Jun 2013 09:06:59 -0600 [thread overview]
Message-ID: <8761xr8ei4.fsf@gmail.com> (raw)
In-Reply-To: 878v2rsfol.fsf@krugs.de
> the tangled file looks as follow, including the empty lines at
> beginning and end:
>
> ,----
> |
> | ## [[file:~/tmp/jumpBack.org::*newASM%20(./newASM.R)][newASM\ \(\./newASM\.R\):1]]
> |
> | logList("##########################################################################")
> | logList("##########################################################################")
> | logList("####")
> | logList("#### Simulation object ASM created.")
> | logList("####")
> | logList("#### It has been undergone basic initialisation and will")
> | logList("#### be initialised for usage when simulated by running")
> | logList("####")
> | logList("#### > sim(ASM)")
> | logList("####")
> | logList("#### or manually, without simulating, by running")
> | logList("#### > ASM <- initialize(ASM)")
> | logList("####")
> | logList("##########################################################################")
> | logList("####")
> | logList( paste("#### GISDBASE : ", parms(ASM)$baseDir) )
> | logList( paste("#### LOCATION : ", parms(ASM)$grassLocation) )
> | logList( paste("#### MAPSET : ", parms(ASM)$grassMapset) )
> | logList("####")
> | logList("##########################################################################")
> | logList("##########################################################################")
> | logEnd()
> | return(ASM)
> | }
> |
> | ## newASM\ \(\./newASM\.R\):1 ends here
> |
> `----
>
> This one works, although the cursor is consistently two characters to the left then
> where it should be.
>
This is off because the first line of your example is not indented
correctly when tangled. Specifically, it is indented by two spaces in
the source file and by four spaces in the code block. Setting the
`org-src-preserve-indentation' variable to t should fix this.
>
> If I change
>
> ,----
> | #+PROPERTY: padline yes
> `----
>
> to
>
> ,----
> | #+PROPERTY: padline no
> `----
>
> the padlines are gone, ant the jumping back is completely off (from
> first r in return() it jumps to the third # in the last logList()).
>
For now I think both padlines and link comments are required for the
jumping functionality to work. I've updated the documentation to
reflect this.
,----
| @subheading Jumping between code and Org
|
| When tangling code from an Org-mode buffer to a source code file, you'll
| frequently find yourself viewing the file of tangled source code (e.g., many
| debuggers point to lines of the source code file). It is useful to be able
| to navigate from the tangled source to the Org-mode buffer from which the
| code originated.
|
| The @code{org-babel-tangle-jump-to-org} function provides this jumping from
| code to Org-mode functionality. Two header arguments are required for
| jumping to work, first the @xref{padline} option must be set to true (the
| default setting), second the @xref{comments} header argument must be set to
| @code{links}, which will insert comments into the source code buffer which
| point back to the original Org-mode file.
`----
--
Eric Schulte
http://cs.unm.edu/~eschulte
next prev parent reply other threads:[~2013-06-06 15:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 14:54 refine org-babel-tangle-jump-to-org? Rainer M. Krug
2013-05-30 22:05 ` Eric Schulte
2013-05-31 7:35 ` Rainer M. Krug
2013-05-31 13:16 ` Eric Schulte
2013-06-03 9:32 ` Rainer M Krug
2013-06-03 13:34 ` Other question concerning org-babel-tangle-jump-to-org Rainer M Krug
2013-06-04 8:33 ` Julian M. Burgos
2013-06-04 8:39 ` Rainer M Krug
2013-06-05 16:10 ` Julian M. Burgos
2013-06-06 15:13 ` Eric Schulte
2013-06-07 7:27 ` Rainer M Krug
2013-06-06 15:06 ` Eric Schulte [this message]
2013-06-07 8:26 ` refine org-babel-tangle-jump-to-org? Rainer M Krug
2013-06-07 12:29 ` Rainer M Krug
2013-06-07 15:24 ` Eric Schulte
2013-06-07 15:38 ` Rainer M Krug
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=8761xr8ei4.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=Rainer@krugs.de \
--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).