Eric Abrahamsen writes:
> Carsten Dominik writes:
>
>> Dear all,
>>
>> before continuing this discussion, and before reinventing, you might
>> want to take a look at how org-id.el currently does create unique IDs.
>> [...]
>> Hope this helps.
>
> Right, and we're not trying to reinvent any wheel
Carsten Dominik writes:
> Dear all,
>
> before continuing this discussion, and before reinventing, you might
> want to take a look at how org-id.el currently does create unique IDs.
> In particular, take a look at these variables:
>
> org-id-prefix
> org-id-method
> org-id-include-domain
>
> In
And one more remark.
A main reason for the CUSTOM_ID (and my only use of it, really) it to make
HTML targets stable and meaningful. In the following file
*
*
:PROPERTIES:
:CUSTOM_ID: Lotsofbshere
:END:
you can have a stable link
to file.html#Lotsofbshere
Carsten
On Thu, Dec
Dear all,
before continuing this discussion, and before reinventing, you might want
to take a look at how org-id.el currently does create unique IDs. In
particular, take a look at these variables:
org-id-prefix
org-id-method
org-id-include-domain
In particular, the docstring of the variable org
Christophe Schockaert writes:
> Eric Abrahamsen writes:
>
>> Karl Voit writes:
>>
>>> I'd prefer using manually written :ID: instead since migration would
>>> not be trivial to me.
>>
>> You could also use the `org-property-set-functions-alist' trick with the
>> :ID: property. If you added an "I
Eric Abrahamsen writes:
> Karl Voit writes:
>
>> I'd prefer using manually written :ID: instead since migration would
>> not be trivial to me.
>
> You could also use the `org-property-set-functions-alist' trick with the
> :ID: property. If you added an "ID" entry to that alist, Org's usual
> aut
John Kitchin writes:
> On Thu, Dec 22, 2016 at 10:30 AM, Karl Voit wrote:
>
>> * John Kitchin wrote:
>> >
>> > There is not an issue using a human-readable id in :ID: as long as it is
>> > unique. It will store fine, link fine, etc...
>>
>> I also think so because I am only using human-readable
an example of a custom id feature might be for export. sounds like
you might not need it.
On 12/22/16, Karl Voit wrote:
> However, the argument was that no human should set :ID: but use
> :CUSTOM_ID: *instead*. See also the old thread I linked before.
i don't recall anybody arguing, claiming, or implying specifically that.
if you're careful, and do not need custom id features, then y
Karl Voit writes:
> * John Kitchin wrote:
>>
>> There is not an issue using a human-readable id in :ID: as long as it is
>> unique. It will store fine, link fine, etc...
>
> I also think so because I am only using human-readable :ID: without
> any issue so far.
>
> However, the argument was that
That is just be a convention though, and as long as the IDs are unique, it
does not matter who sets them.
John
---
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
* John Kitchin wrote:
>
> There is not an issue using a human-readable id in :ID: as long as it is
> unique. It will store fine, link fine, etc...
I also think so because I am only using human-readable :ID: without
any issue so far.
However, the argument was that no human should set :ID: but use
There is not an issue using a human-readable id in :ID: as long as it is
unique. It will store fine, link fine, etc...
John
---
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
* Karl Voit wrote:
> * Samuel Wales wrote:
>> On 12/18/16, Karl Voit wrote:
>>> Usually, my IDs start with the current ISO day to enforce uniqueness
>>> and look like this:
>>
>> my understanding, which might be incorrect, is that custom id is for
>> human-readable purposes, while id is for
* Samuel Wales wrote:
> On 12/18/16, Karl Voit wrote:
>> Usually, my IDs start with the current ISO day to enforce uniqueness
>> and look like this:
>
> my understanding, which might be incorrect, is that custom id is for
> human-readable purposes, while id is for uuid. although you could
>
15 matches
Mail list logo
