From: Ihor Radchenko <yantar92@posteo.net>
To: Tor Erlend Fjelde <tor.github@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Feature request: IDs for everything
Date: Sat, 21 Oct 2023 13:05:35 +0000 [thread overview]
Message-ID: <87o7gst9b4.fsf@localhost> (raw)
In-Reply-To: <877cnhyuom.fsf@tor-Prestige-15-A10SC.mail-host-address-is-not-set>
Tor Erlend Fjelde <tor.github@gmail.com> writes:
> I was wondering if there's a reason why we couldn't have IDs a la
> org-id.el for everything? It seem to me that it would be useful to use
> something like `#+ID` in place of `#+NAME` for tables, blocks, etc. as
> well as headlines.
This has been discussed in the past.
Apart from #+NAME, we also have radio <<<targets>>> that can be used a
link anchors (#+NAME or other affiliated keywords are not allowed, for
example, in items).
We also discussed linking to #+name and <<<target>>> globally, without
specifying the file path.
> Would this go against the intended design of
> org-id.el, or is this a change that would be welcome but that no one
> has gotten around to implementing yet?
Mostly nobody has gotten around.
Although we have at least one caveat that we need to consider - the
current users of the id: links blindly assume that they always link to
headings. This includes many third-party packages, like org-roam.
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. For
example, `org-id-find' and other API function may need to work in two
modes: (1) legacy, only searching for headings; (2) new, searching for
anything. This can, for example, be done via an extra optional argument.
-----
As an alternative option, we had a proposal that extends id: links to
have a search option:
[[id:<ID>:search-string]]
Then, we may have top-level drawer like
:PROPERTIES:
:ID: unique-file-id
:END:
And then refer to anything inside the file as
[[id:unique-file-id:object-id-inside-the-file]]
--
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-10-21 13:05 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 [this message]
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
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=87o7gst9b4.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--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).