From: Max Nikulin <manikulin@gmail.com>
To: Tor Erlend Fjelde <tor.github@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Feature request: IDs for everything
Date: Thu, 26 Oct 2023 16:20:40 +0700 [thread overview]
Message-ID: <8a536d19-0686-486e-8d8a-33534cb79aee@gmail.com> (raw)
In-Reply-To: <87o7gst9b4.fsf@localhost>
On 21/10/2023 20:05, Ihor Radchenko wrote:
> Tor Erlend Fjelde 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.
I think, another complication is referring source code blocks as
variable values in header arguments and as noweb fragments. It would be
great to be possible to specify "id:UUID" instead of fuzzy names.
Perhaps it may be solved by explicit calls to new functions. If
possible, I would avoid proliferation of keyword in favor of "#+name:
id:UUID"
And there are references to particular lines inside code blocks...
> 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).
I think, you mean <<anchors>>, not <<<radio>>> targets that activates
plain text words. It seems, the latter cannot be currently exported as
explicit links [[radio][Radio]]. I am unsure what conflicts may appear
during attempt to allow optional explicit types, e.g. <<id:UUID>>.
> We also discussed linking to #+name and <<<target>>> globally, without
> specifying the file path.
From my point of view, it should be either global id:UUID links or
file:doc.org::name local links.
> 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?
> [[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.
next prev parent reply other threads:[~2023-10-26 9:54 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 [this message]
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=8a536d19-0686-486e-8d8a-33534cb79aee@gmail.com \
--to=manikulin@gmail.com \
--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).