Eric Schulte <schulte.e...@gmail.com> writes: >> 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("##########################################################################")
[snip (19 lines)] >> | 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. > Thanks - I will change it accordingly. Rainer [snip (16 lines)] <#secure method=pgpmime mode=sign> -- Rainer M. Krug email: RMKrug<at>gmail<dot>com