Hi Samuel, I do remember the earlier discussion we had about this. I can see how using IDs for more localized linking could be useful, and how this kind of extensible syntax could be useful. I do hav
Hi, Lots of interesting ideas, and cool syntax options. My one proposed modification would be to only allow linking down to the table or list level, and then use existing reference syntax combined w
Hi, Lots of interesting ideas, and cool syntax options. My one proposed modification would be to only allow linking down to the table or list level, and then use existing reference syntax combined wi
Now seems like an ideal time to post this. I have been thinking that it would be useful to be able to slap org IDsonanything. This includes plain list items, table cells, and specific words in long
Hi sindikat, ... Yes, you got it. Wherever an ID marker is, that place is a graph vertex. Because it uses Org IDs, it is pretty unbreakable and can be linked to across files. If you move it, you don'
Apparently my post wasn't connected to the original thread, so here it is - http://lists.gnu.org/archive/html/emacs-orgmode/2009-03/msg00176.html Samuel, may be i will start implementing something li
I really love this idea of ID markers. It would open so many opportunities for semantic extensions of org-mode and not only. Using ID markers we can make a associative array (map, dict, key-value sto
I wrote this a long time ago in response to Carsten's reply to Eric in the first link below. == 1) http://thread.gmane.org/gmane.emacs.orgmode/11896 extensible syntax with an application in id marker
This is a very good point, and definitively makes things non-trivial. Nonetheless, I'd be happy to have a go at it if this seems like the way to go! But I'll probably need quite a bit of help in the
This has been discussed in the past. 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).
This is a moderately difficult contribution. As a first step, you will need to study org-id.el and see what should be changed there to support the new feature. If you encounter any difficulties, feel
Hi Samuel, I have now read through your proposal. To me it seems that using ID's is the best way forward. Right now I am working on (in fact have for some time) to greatly improve the usability of En
Where is the profile? I like note-taking researcher profiles. 🤓 Good that I have given up on that puzzle of making Org database, rather using PostgreSQL database straight, and deriving Org out of
hi lawrence, as eric and nick pointed out, you can use properties with org-id to implement arbitrary graphs. you will have to write the code to select the children and go to them and go back. org-id'