-
Notifications
You must be signed in to change notification settings - Fork 6
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
Why the order is not respected ? #32
Comments
I think I've found the solution: |
Hi @Cletip , thanks for the update. Really nice that you found it. Do you think this should be changed or maybe exposed to the user to customize that? Best, |
Hello @jgru ! I think you should delete the line: if it's nil, then I don't think it's useful (because it's nil, but the order was modified because of the nil : it's not the behavior that we want, we want to not touch the order !). On the other hand, I don't know how the underlying of consult, so you'd have to check that it doesn't interfere with other things (and explain that the consult-org-roam-buffer-enabled variable just enables org-roam buffers in consult-buffer, and not doesn't change the order, for example). So yes, to sum up, delete the line (and maybe explain the consult-org-roam-buffer-enabled variable in more detail in the readme ?). Best too, |
I was looking for this too - I realised this was broken, when trying to test a cache to the It was turned off in the first place because user complained that org-roam's sort was failing and being overriden -- if I am not incorrect? If I may ask why is the history commented out? Thanks. |
Also I want to note that I think org-roam's atime implementation is broken. the atime is stored in a node -- but nodes are not updated unless some change is pushed -- so the atime sort is bound to fail. atime and mtime are functionally the same. For test,
Youll notice that the atime doesn't change if you simply visit the file. So its broken because the atime sort is broken in org-roam and users notice this as a fault of consult-org-roam because it relies on sort passed by org-roam -- my guess. Please correct me if you have different result in your query. But if this is true -- it should default to nil - and force the user to either roll out their own sort-fn or get the sort function of their minibuffer by setting :sort to t -- which will override org-roam's. |
My hunch was correct - it is indeed calling vertico-sort when :sort is set to t --
Should clarify this issue in the visible place to clear confusion, And also let users configure it through a |
Hi there!
Related to #28 : the proposed solution does not work :(
When I try to do this :
I always get the same order, regardless of whether the consult-org-roam-buffer-enabled variable is nil or t by the way.
I don't understand why I have this behaviour. The desired behaviour would be when I don't activate consult-org-roam (I use vertico-prescient, and I simply have a sort by date of node visited, which is very good) but I no longer have the preview (which is disturbing, because I really love that one).
Is there a solution? Have I misunderstood something?
Thank you in advance for your reply.
The text was updated successfully, but these errors were encountered: