From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id cGNoMllLOmVzNgAA9RJhRA:P1 (envelope-from ) for ; Thu, 26 Oct 2023 13:19:53 +0200 Received: from aspmx1.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id cGNoMllLOmVzNgAA9RJhRA (envelope-from ) for ; Thu, 26 Oct 2023 13:19:53 +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 38EE742C82 for ; Thu, 26 Oct 2023 13:19:53 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=kJ0RSyxV; 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=none) header.from=posteo.net ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1698319193; 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=smTk9/DUZTD3lOEiMg8lERNGYgPYj7m5bsF64AFL5sw=; b=KDCxBbfmRBMo3iUnBJhTHA1JZeZHT59C4DctmIDuvTJNhVXEKVWv6VZicyNTHx1d2k7+Dt d8BpWiRY41UiilC8coy756AvGG/qeGZhTrjKTTJoZ9HiRUTEnSO/iwut7igfqUPqsLFjMx q0im0fCzrhGBrypdcwaimHu+6kbdkpl/dRqJ3P0jJLuWlARavVsq7+Z43enUDUKYeRs91L FoykgjSzLzDS2klu73p0aU7EOLu0bn7tR8LiezpVrpZL5bFlSTHzYIFKcjuZQFc54oVY97 WeI+IgWLiKijYE2eH+TYjkGZD9Cxfcw3fODJbvXdrf7bR1hIPx8LKC6Py363Og== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=kJ0RSyxV; 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=none) header.from=posteo.net ARC-Seal: i=1; s=key1; d=yhetil.org; t=1698319193; a=rsa-sha256; cv=none; b=V+m5ElyYoNZ/Z6xFipfWVSIz/n5CjquUgdU36B2zjz3l+AJA9fJXqxxcDAmhN/HPvoXbId pH8eqE2v0CTNTm3SwIjxnqE7qsArcEyUgtBWLYpVlmbQkz60MuIeGVrBV9Cc2yzGuTWuR7 eI8NsHEf62WEZzSga6oQl8bW4RfLsEt/DWeFvGfEAtZnVKoqYcZiV4KeeOHI/7fbPimz+k 4Q6OMGfcUQKTviJ2lxY7Gfho7Z52EdUSzAptqvZdPPOv7gkUyVN4x9fcI6P7ba/IWVPvFf RnyDvoHKm9ApX+VhBF+GV5Yu0ZW6+GVZ0ckhB5q/2FmTw0cUb9KAUFNtUWBbFQ== Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qvyNy-0006QI-7i; Thu, 26 Oct 2023 07:18:46 -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 1qvyNt-0006Q4-3t for emacs-orgmode@gnu.org; Thu, 26 Oct 2023 07:18:41 -0400 Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qvyNq-0007qu-CL for emacs-orgmode@gnu.org; Thu, 26 Oct 2023 07:18:40 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 4FF03240029 for ; Thu, 26 Oct 2023 13:18:36 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1698319116; bh=Jsozi53qUcjRtkQ32XzvNbeiE43nhiDf6Rgzep3fI2g=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=kJ0RSyxVqj1sgO6tJSJQ1reb0/um4pZgal3Qv8Dy4nUL8QMPNbcxfoyGUJ+qK0Bdq uAYmCH7qgIZzXd2eOpgTf74Xc84vUNsLDK3ytLiMdmvl6EDbtWkybqTpCJ8jOorifT Erp3UjbTj0+XGtgHtBpxEu//kAPTm+DMbfQtcMvDMKxtE/HDz/3/n+mC3z+kAX6DOY jmpTYzwye1EU0JISvJ5JsV0IWf9MNzenHT//TjNQDSHj0rDcIpLN/UpzcSM5EzIxw8 GwZJXLu3QKx5S82xq3iRYHL3C2L8GUsC8R6YGFr7NjQ5YPmfBFCmc05IIYPLXIUZYL y+sCETyGIDW0A== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4SGNZz0lLXz9rxL; Thu, 26 Oct 2023 13:18:34 +0200 (CEST) From: Ihor Radchenko To: Max Nikulin Cc: Tor Erlend Fjelde , emacs-orgmode@gnu.org Subject: Re: Feature request: IDs for everything In-Reply-To: <8a536d19-0686-486e-8d8a-33534cb79aee@gmail.com> References: <877cnhyuom.fsf@tor-Prestige-15-A10SC.mail-host-address-is-not-set> <87o7gst9b4.fsf@localhost> <8a536d19-0686-486e-8d8a-33534cb79aee@gmail.com> Date: Thu, 26 Oct 2023 11:20:16 +0000 Message-ID: <877cn9d40f.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 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: -6.30 X-Spam-Score: -6.30 X-Migadu-Queue-Id: 38EE742C82 X-TUID: XUmbqf28r0X1 Max Nikulin writes: >> If we simply allow id: links to point to non-headings, it will be a >> major breaking change that may affect third-party packages. So, we >> need to design the extended ids carefully to avoid breakage. > > A defcusom user options whether id:UUID links for non-heading elements > are allowed. It is just an opinion/idea and nothing more. > Are ids for whole files (placed before first headings) are problematic > for 3rd party packages? Fair point. Even existing id links may not always point to a heading (when pointing to IDs in top-level property drawer). So, the potential breakage I was talking about is already there, and third-party packages already have to adapt. I still do not feel confident that it will be safe to blindly change org-id in the proposed way though. Although I cannot think of clear examples why it would cause problems worse compared to the existing id: links to files. So, it may just be my unmotivated concern. >> [[id:unique-file-id:object-id-inside-the-file]] > > Perhaps than it should be id:FILE-UUID::SEARCH with usual search options > like #CUSTOM_ID, *Heading, etc., with the new variant id:OBJECT-UUID. > However I am unsure if search should be limited to a subtree if > HEADING-UUID is specified instead of FILE-UUID. I indeed meant "::" search option. Sorry for the typo. In any case, I agree with Tor that search option is less elegant. If we can go for direct UUIDs, let's do it. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at