Re: Properties ID vs. CUSTOM_ID

[Christophe Schockaert <R3vLibre@citadels.eu>]

Eric Abrahamsen writes:

> Carsten Dominik <dominik@uva.nl> 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 wheels, just get a
> user-readable string in there while still retaining uniqueness. Ie, it
> would probably be enough if org-id-prefix could be set to 'entry, and
> org then generated a prefix by munging the entry text:
>
> * My Great Header
>   :PROPERITIES:
>   :ID: my-great-header-44d1-b804-d11657131237
>   :END:
Sounds good to me.


I still like the idea to be able to use a plain date, but when I need
it, I would most than probably set it as an inactive timestamp in the
entry title in my case. It would thus be addressed if the "munging"
would also handle cleverly the timestamp in an entry title (which it
should do anyway I think).

So, from my perspective, this approach fully fulfill the needs in an
efficient way.


Christophe

-- 
--------------->  mailto:R3vLibre@citadels.eu
Once it's perfectly aimed, the flying arrow goes straight to its target.
Thus, don't worry when things go right.
There will be enough time to worry about if they go wrong.
Then, it's time to fire a new arrow towards another direction.
Don't sink.  Adapt yourself !  The archer has to shoot accurately and quickly.
[Words of Erenthar, the bowman ranger] <---------------<<<<