From: TRS-80 <firstname.lastname@example.org> To: email@example.com Subject: Re: Any reason not to generate my own custom ID value (NOT CUSTOM_ID)? Date: Thu, 10 Sep 2020 21:31:43 -0400 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <87pn6ti0kt.fsf@localhost> On 2020-09-10 21:06, Ihor Radchenko wrote: >> I do appreciate all the replies so far. However as I plan on relying >> on this to implement some quite critical functionality for a package I >> am working on (a sort of Zettelkasten / TiddlyWiki in Orgmode if you >> will) I would feel a lot more comfortable with some additional >> reassurences that what I am planning is not some crazy or bad idea. > > Is there any particular reason why you even need to display :ID: value > to > the user? If only id: links are concerned, link description can be made > short and human-readable. > > Best, > Ihor Yes, most of the time I expect I will be using Orgmode double bracket style links which will, as you say, hide the id: from the user, allowing to replace it with whatever desired text in the form of the link description. However, I just (strongly) prefer the shorter "ISO-like" ID for many reasons, as already mentioned (shorter, meaningful, etc.). I just find that style much, much more elegant. Besides, as an ID, they are plenty "Unique" for my use case, with the default minute resolution (however even that, is configurable in my implementation, by way of a time-format variable, should anyone need more). I suppose if we ever get to a world where people start linking to each others' individual publicly published zettel, I may regret the decision. However Ted Nelson has already been working on such a thing for some decades already, and we are still not there yet, so I don't think I will need to worry about that any time soon. ;) Even if so, it would be a very small implementation change anyway. Cheers, TRS-80
next prev parent reply other threads:[~2020-09-11 1:32 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-10 20:02 TRS-80 2020-09-10 22:00 ` Gustav Wikström 2020-09-10 22:16 ` TRS-80 2020-09-13 20:18 ` Bastien 2020-09-10 22:20 ` Samuel Wales 2020-09-10 23:33 ` TRS-80 2020-09-11 1:06 ` Ihor Radchenko 2020-09-11 1:31 ` TRS-80 [this message] 2020-09-11 7:51 ` Ihor Radchenko 2020-09-13 20:19 ` Bastien 2020-09-23 7:19 ` Bastien 2020-09-23 7:43 ` [PATCH] " Ihor Radchenko 2020-09-23 7:48 ` Bastien 2020-09-23 8:08 ` Ihor Radchenko 2020-09-23 8:30 ` Bastien 2020-09-23 8:40 ` Ihor Radchenko 2020-09-23 8:48 ` Bastien 2021-04-25 14:19 ` Bastien
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Any reason not to generate my own custom ID value (NOT CUSTOM_ID)?' \ /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
Code repositories for project(s) associated with this 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).