From: Vincent Picaud <picaud.vincent@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [BUG] generated ":comment link" when tangling babel src blocks are not complete (or buggy)
Date: Wed, 7 Dec 2022 19:04:14 +0100 [thread overview]
Message-ID: <CAJGQD+yQPK7BAzW=4xPL4A=H35z4-C+mRz+mw7o1znQioKH0SQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]
When I tangle code "C-c C-v t" of this org-mode file:
#+title: Demo
#+property: header-args:sh :tangle example.sh :comments link
* Part A
** source
#+begin_src sh
echo "Part A"
#+end_src
* Part B
** source
#+begin_src sh
echo "Part B"
#+end_src
I get this example.sh file
# [[file:poub.org::*source][source:1]]
echo "Part A"
# source:1 ends here
# [[file:poub.org::*source][source:1]]
echo "Part B"
# source:1 ends here
Now I move to the line "echo "Part B"" of this example.sh file and call
org-babel-tangle-jump-to-org. This causes me to jump back to the
org-mode file as expected, but it jumps to the "* Part A" heading instead
of the right "* Part B" heading.
If I manually modify the generated example.sh file as follows
# [[file:poub.org::*source][source:2]]
echo "Part B"
# source:2 ends here
then org-babel-tangle-jump-to-org works correctly and jumps back to
right "* Part B" header's source block.
Do you observe the same behavior ? Is there a way to get expected behavior
(still having 2 headings with the same "source" name) ?
Thanks,
despite that, org-mode is awesome! :)
Emacs : GNU Emacs 28.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.34, cairo version 1.16.0) of 2022-11-09
Package: Org mode version 9.6 (9.6-gc59d6d @
/home/picaud/.emacs.d/straight/build/org/)
[-- Attachment #2: Type: text/html, Size: 14199 bytes --]
reply other threads:[~2022-12-07 18:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAJGQD+yQPK7BAzW=4xPL4A=H35z4-C+mRz+mw7o1znQioKH0SQ@mail.gmail.com' \
--to=picaud.vincent@gmail.com \
--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).