From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Tobias Müller" <mllertobias@gmx.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: problems with tangled code [8.3.2 (8.3.2-51-g713fe8-elpa @ /home/tobias/.emacs.d/elpa/org-20151221/)]
Date: Sat, 02 Jan 2016 17:08:01 +0100 [thread overview]
Message-ID: <871ta0j76m.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <5680563C.3020807@gmx.de> ("Tobias \=\?utf-8\?Q\?M\=C3\=BCller\=22's\?\= message of "Sun, 27 Dec 2015 22:21:00 +0100")
Hello,
Tobias Müller <mllertobias@gmx.de> writes:
> I have discovered a problem with tangled source code in org-mode. As a
> minimal example I set up the following in a file ~/test.org
>
> * Section
> Some Text
> #+BEGIN_SRC python :tangle files/file.py :comments link
> print('Block 1')
> #+END_SRC
>
> More Text
> #+BEGIN_SRC python :tangle files/file.py :comments link
> print('Block 2')
> #+END_SRC
>
> If I tangle the file with C-c C-v t the resulting file ~/files/file.py
> looks like this:
>
> # [[file:test.org::*Section][Section:1]]
> print('Block 1')
> # Section:1 ends here
>
> # [[file:test.org::*Section][Section:1]]
> print('Block 2')
> # Section:1 ends here
>
> The 1st problem here is, that the code-block counter seems not to work,
> because both code blocks are labeled as [Section:1], so if I want to use
> org-babel-tangle-jump-to-org both blocks would jump to block 1.
> Furthermore the location of the .org file is not correctly indicated,
> since the
> .org file is located at ~/test.org and not in the ~/files directory, so
> org-babel-tangle-jump-to-org tries to create a new file
> ~/files/test.org.
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2016-01-02 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-27 21:21 Bug: problems with tangled code [8.3.2 (8.3.2-51-g713fe8-elpa @ /home/tobias/.emacs.d/elpa/org-20151221/)] Tobias Müller
2016-01-02 16:08 ` Nicolas Goaziou [this message]
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=871ta0j76m.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=mllertobias@gmx.de \
/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).