From: Titus von der Malsburg <malsburg@posteo.de>
To: emacs-org list <emacs-orgmode@gnu.org>
Subject: Problem with org-babel-detangle
Date: Fri, 29 Jan 2016 16:34:57 -0800 [thread overview]
Message-ID: <87h9hvkiq6.fsf@posteo.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]
I tangeled the following org-mode file:
#+BEGIN_SRC R :tangle /tmp/test.R :comments link
1 + 2
#+END_SRC
#+BEGIN_SRC R :tangle /tmp/test.R :comments link
3 + 4
#+END_SRC
The result was:
## [[file:test.org][No\ heading:1]]
1 + 2
## No\ heading:1 ends here
## [[file:test.org][No\ heading:2]]
3 + 4
## No\ heading:2 ends here
Then I changes “3 + 4” to “3 + 5”, revisited the org buffer, and
executed `org-babel-detangle'.
Expected behavior: The second code block in org file is updated to contain
“3 + 5”.
Actual behaviour: I find myself in a buffer containing test.R, the
cursor is inside the first code block at “1”, the second code block’s
content in the org buffer is highlighted, and I have an edit buffer for
that code block. The content of the second code block is not updated.
No error message.
Tested with a current development Emacs and the development version of
org-mode.
I think the culprit is `org-babel-tangle-jump-to-org'. When I call it
in test.R, it does not jump to the org file as it should according to
the documentation.
When I call it with point on the first code block, it opens an edit
buffer for the second code block in the background.
When I call it with point on the second code block, it opens test.org in
the background but doesn’t do anything else.
Titus
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next reply other threads:[~2016-01-30 0:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 0:34 Titus von der Malsburg [this message]
2016-01-31 19:50 ` Problem with org-babel-detangle Nicolas Goaziou
2016-01-31 20:32 ` Titus von der Malsburg
2016-02-02 22:29 ` Nicolas Goaziou
2016-02-02 22:37 ` Titus von der Malsburg
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=87h9hvkiq6.fsf@posteo.de \
--to=malsburg@posteo.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).