From: Ihor Radchenko <yantar92@posteo.net>
To: Evgenii Klimov <eugene.dev@lipklim.org>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [FR] Add an option to use ID links during tangling
Date: Fri, 28 Jul 2023 07:46:48 +0000 [thread overview]
Message-ID: <87fs58fpg7.fsf@localhost> (raw)
In-Reply-To: <878rb1v3f8.fsf@lipklim.org>
Evgenii Klimov <eugene.dev@lipklim.org> writes:
> I see in the comment there the reason for that, but still would prefer
> to use unique IDs in tangled files: the probability to overwrite wrong
> source block under nonunique header overweights a side-effect of
> creating new ID in Org file during tangling.
Did you actually encounter such situation?
`org-babel-detangle' is far from ideal in general.
For example, detangling noweb references is pretty much guaranteed to
create mess.
> Can we do something with this? Add another option or provide an even
> eager value in =org-id-link-to-org-use-id=.
I do not like the idea of creating side effects in the original Org
document during tangling.
We can, however, use (org-id-link-to-org-use-id 'use-existing) to use
the already present IDs.
Ideally, we should improve the detangling to understand the order of
blocks better instead of searching the containing heading independently.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-07-28 8:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 14:20 [FR] Add an option to use ID links during tangling Evgenii Klimov
2023-07-28 7:46 ` Ihor Radchenko [this message]
2023-07-28 10:13 ` Evgenii Klimov
2023-07-28 10:35 ` Ihor Radchenko
2023-08-08 12:58 ` Ihor Radchenko
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=87fs58fpg7.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=eugene.dev@lipklim.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).