From: Ihor Radchenko <yantar92@posteo.net>
To: Max Nikulin <manikulin@gmail.com>
Cc: Tor Erlend Fjelde <tor.github@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Feature request: IDs for everything
Date: Thu, 26 Oct 2023 11:20:16 +0000 [thread overview]
Message-ID: <877cn9d40f.fsf@localhost> (raw)
In-Reply-To: <8a536d19-0686-486e-8d8a-33534cb79aee@gmail.com>
Max Nikulin <manikulin@gmail.com> 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 <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2023-10-26 11:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 19:12 Feature request: IDs for everything Tor Erlend Fjelde
2023-10-20 22:11 ` Rodrigo Morales
2023-10-21 9:04 ` Tor Erlend Fjelde
2023-10-21 13:05 ` Ihor Radchenko
2023-10-26 6:35 ` Tor Erlend Fjelde
2023-10-26 8:56 ` Ihor Radchenko
2024-03-06 11:52 ` Ihor Radchenko
2024-03-06 12:20 ` Tor Erlend Fjelde
2023-10-26 9:20 ` Max Nikulin
2023-10-26 11:20 ` Ihor Radchenko [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=877cn9d40f.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
--cc=tor.github@gmail.com \
/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).