I think that this is not necessarily vulpea's job directly, but it might be interesting to talk about it here, because vulpea has a solid base to do this kind of thing.
To describe my point in more detail, I noticed this:
a query-based system is much more efficient than a simple search system
search and insert is in the end almost the same thing from the user's point of view (search for a certain note/node, then insert or go to that note/node)
org-ql is incredibly powerful, but doesn't work for org-roam/vulpea (because most nodes are files.)
So my desire is to unify these three components:
create a "super function" that would search for a note based on all possible parameters:
title (already done, build-in in vulpea)
value of one or more metadata (already done)
backlinks (already done)
tag (already done too)
etc
The interface would be close to org-ql. Maybe we should make queries like them, with predicates? I don't know, because it takes away from the simplicity, no? Anyway, that's another problem.
Then, after finding the right note(s), we could do actions on them: insert them, go to a note, others...
This will not happen overnight, but most functions can do without vulpea notes as an intermediary. (I'm not sure if this statement is correct in English)
As I said, vulpea may not be the best place, but this package has almost everything, it is almost enough to assemble the bricks already made (already, the fact that vulpea-find and vulpea-insert both use "vulpea-select" is a proof of this tendency to want to unify the search and insert system. It's genius to have done this).
The point is, I want your opinion! What do you think?
Personally, I think it's doable, it's almost revolutionary, but I'm afraid it's time for nothing in the sense that it's not an essential feature. Even if, currently, to insert a note, the way it works is: search for the title. If the title not enough, do a more thorough manual search (by ripgrep, org-ql, or another system of search), save the title in your memory, go back to the note where do you want to insert the link to the note, recall the insert function, enter the title, press enter.
This works perfectly, but in the end, it is a tinkering compared to a unification of the search and insert systems.
Hi!
I think that this is not necessarily vulpea's job directly, but it might be interesting to talk about it here, because vulpea has a solid base to do this kind of thing.
To describe my point in more detail, I noticed this:
So my desire is to unify these three components: create a "super function" that would search for a note based on all possible parameters:
The interface would be close to org-ql. Maybe we should make queries like them, with predicates? I don't know, because it takes away from the simplicity, no? Anyway, that's another problem.
Then, after finding the right note(s), we could do actions on them: insert them, go to a note, others...
This will not happen overnight, but most functions can do without vulpea notes as an intermediary. (I'm not sure if this statement is correct in English)
As I said, vulpea may not be the best place, but this package has almost everything, it is almost enough to assemble the bricks already made (already, the fact that vulpea-find and vulpea-insert both use "vulpea-select" is a proof of this tendency to want to unify the search and insert system. It's genius to have done this).
The point is, I want your opinion! What do you think?
Personally, I think it's doable, it's almost revolutionary, but I'm afraid it's time for nothing in the sense that it's not an essential feature. Even if, currently, to insert a note, the way it works is: search for the title. If the title not enough, do a more thorough manual search (by ripgrep, org-ql, or another system of search), save the title in your memory, go back to the note where do you want to insert the link to the note, recall the insert function, enter the title, press enter. This works perfectly, but in the end, it is a tinkering compared to a unification of the search and insert systems.