Hi,
Oleh Krehel <o.krehel@tue.nl> writes:

>> As for requiring org-id for `org-open-at-point', I'm not sure this
>> is the right thing to do since it will require it for all users, even
>> those who don't use org-id at all.

> The issue is that the current solution isn't portable.[...]
> In my opinion it would be best to require 'org-id implicitly so that
> the links work the same for all users.

We could have a lazy loading of the file in case the "id:" string is
encountered. Actually, we could have a lazy loading of a default package
for each supported link. That would avoid the pain of loading the
package when users don't use it and still make those links work.

IIRC, the difficulty of that solution is that each package implementing
a link (like org-id) explicitly registers to indicate it can handle some
link while my solution assumes that there is some knowledge of which
package handle what link before loading it. For that reason, it is not
so easy to implement. I guess though that the behavior is more close to
what we should want to have.

-- 
Konubinix
GPG Key    : 7439106A
Fingerprint: 5993 BE7A DA65 E2D9 06CE  5C36 75D2 3CED 7439 106A