-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show backlinks from :PROPERTIES:
#41
Comments
Does orgmode support links in the properties drawer? This plugin uses nvim-orgmode to find links within a file and then index id links, so it would need to be handled upstream in that plugin to support links there. In the meantime, you'd need to include your link somewhere else (heading or body) for it to be available. |
So in Doom Emacs I can go to links in properties drawer, but from looking around this seems to be not-according-to-spec. From: https://www.orgroam.com/manual.html
|
If the org AST doesn't support links in property drawers by default, then I don't believe nvim-orgmode will support them, either. I'm totally happy to have this feature added to this plugin, but can't guarantee I'll get to this myself. Happy to review a pull request, though! |
I believe that's completely fair!
Well it doesn't help that I'm new to orgmode/neovim as well :P. |
You can see how it's done in nvim-orgmode https://github.com/nvim-orgmode/orgmode/blob/master/lua/orgmode/files/file.lua#L679-L697. |
Oh that is pretty cool! That would entail something like this: local ts_query = ts_utils.get_query([[
(paragraph (expr) @links)
(drawer (contents (expr) @links))
(property_drawer (value (value) @links))
(headline (item (expr)) @links)
]]) The |
@zetashift yes, something like that, but you would need to write the surrounding logic also to get the links for org-roam. |
So I have a reading list, with books for example:
Now when I'm on the authors page I expect to see backlink to the that properties drawer/book name. Currently the quickfix window is completely empty.
Is it possible to do this or is there maybe a better way to organize this?
The text was updated successfully, but these errors were encountered: