From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id wE50NpaZw2TwmwAASxT56A (envelope-from ) for ; Fri, 28 Jul 2023 12:33:58 +0200 Received: from aspmx1.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id uII0NpaZw2R+UgEAauVa8A (envelope-from ) for ; Fri, 28 Jul 2023 12:33:58 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 89EF644264 for ; Fri, 28 Jul 2023 12:33:58 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=lipklim.org header.s=key1 header.b="31/SvwpR"; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=quarantine) header.from=lipklim.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1690540438; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=15ekC90brK9eTuQ6l2EtI5r8/iyOdPqrRNvMmi/dZT8=; b=D6RwUMfgcGcrXHc4PXkeQM/rD5CAHuuxDVPXaaP8FpZS+IJ3+VF/NdD3EJM4bQ3X1W9VJy o2+Y01OnMbPU6s99hPMWjr4ZUfsOU9Vh9n8TxRIj0WtUItGtEEBxJnRbg3KjzErvaZUM1X 9dXoRqWzAf1CwUEOOKOgJvItOLNtWLYOWeTUelUl8jarnemDmiCGjLdu+ofbp+MDCr1hYb l/wiGVd/t+K1GCfTAxzz9tNt2rZCDC3H6c/fQbSZf1PyO1MtCeFF9ZKCWrb/BBacwZftSa 0KbVBaQEfuOUWiIXTB54ay6ddedvEkVszAy5A5tZBCFajjvp1PsKnmTIRec+Lg== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1690540438; a=rsa-sha256; cv=none; b=fsW339UyqcNOwguK5UYIJMpZIpuO8vH1rN+Z8n7wygWH9GVCQdOHgEceGw3WSdneaZ1yO+ gKTqOitKNw0Dkp0GtF33mSuUbOBaQ6fFS5mtA8P1KrvO35Tf6l96zxWecMaXV4PgsYiVYX N27cdUtGA/6E0yD7CYclnpR+rz5AeaiHelMvDP7Gwz1MpRPc4RxEz+ckUro6KUh0pyvRHC WpwM8TQe2CaE8pmYHfyC6QaJtd7fFUZ7Lm51gykuuMWhEWCWBggkk/4aF7F65/fBLM2OI9 m5VgWITWDbbn8ClkZKWCAfapVzG/0V3MufMywejqnQTwbLZxlLu0C78wouhxRw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=lipklim.org header.s=key1 header.b="31/SvwpR"; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=quarantine) header.from=lipklim.org Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qPKVG-0006Ql-5D; Fri, 28 Jul 2023 06:15:22 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qPKVA-0006P4-JG for emacs-orgmode@gnu.org; Fri, 28 Jul 2023 06:15:16 -0400 Received: from out-76.mta0.migadu.com ([2001:41d0:1004:224b::4c]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qPKV5-0006lK-3W for emacs-orgmode@gnu.org; Fri, 28 Jul 2023 06:15:15 -0400 References: <878rb1v3f8.fsf@lipklim.org> <87fs58fpg7.fsf@localhost> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lipklim.org; s=key1; t=1690539307; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=15ekC90brK9eTuQ6l2EtI5r8/iyOdPqrRNvMmi/dZT8=; b=31/SvwpRJyipHHnunsgKZs8rjVl34FFAM5xaorW+xSRfEMvD2pE/pQzrThnUhKc3/y8JPn k+oTZoPv+EmZK7ajRGywDxv6Q6LKk9bh/NJIUQRqjERBZDSQe6A/VT6LEXNfoJpt0XQHD2 WZuzlY/p3mCUn2CKntS+pOHmxAjkg68= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Evgenii Klimov To: Ihor Radchenko Cc: Org-mode Subject: Re: [FR] Add an option to use ID links during tangling Date: Fri, 28 Jul 2023 11:13:31 +0100 In-reply-to: <87fs58fpg7.fsf@localhost> Message-ID: <874jlouytx.fsf@lipklim.org> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=2001:41d0:1004:224b::4c; envelope-from=eugene.dev@lipklim.org; helo=out-76.mta0.migadu.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Scanner: mx2.migadu.com X-Migadu-Spam-Score: -8.02 X-Spam-Score: -8.02 X-Migadu-Queue-Id: 89EF644264 X-TUID: nefeCpOO3HGQ Ihor Radchenko writes: > Evgenii Klimov 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. Yes, I did. I keep my whole emacs configuration in an Org file and tangle it after adjustments at Emacs startup (~org-babel-load-file~). Recently I decided to split the tangled file and learned about detangling. And I have a lot of similar headers since my Org file looks like this: #+begin_example * package 1 ** basic ** custom functions ** custom bindings * package 2 ** basic ** custom functions ** custom bindings #+end_example >> 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. Understandable, with (org-id-link-to-org-use-id 'use-existing) I would at least be able to manually add them where needed. > Ideally, we should improve the detangling to understand the order of > blocks better instead of searching the containing heading independently. Maybe recent feature suggestion [1] will be of use here. [1] https://list.orgmode.org/118435e8-0b20-46fd-af6a-88de8e19fac6@app.fastmail.com