Org-roam-node-find sorting unexpectedly!

How To
1

I’m on org-roam v2. I was expecting that the org-roam-node-find will show docs in sorted mtime order, because org-roam-node-default-sort is set to file-mtime by default.

I can see in the sqlite3 database that the nodes data is correct and up to date. I can edit a file / node, and its data is updated correctly.

The org-roam-node-find shows docs, which seem to be somewhat sorted by tags (empty tags, numeric tags, and then alphabets). Not all docs with no tags show at the top.

I’ve done a complete org-roam-db-clear-all and rebuilt the database.

2

Would love to get some responses with what others are seeing, just to determine if it is common, or some issue with my setup.

Does your org-roam-node-find show nodes strictly in modification time order?

3

No. It seems that modification time is adjusted by the alphanumeric order of what appears in each line in minibuffer.

I haven’t looked into this in detail but that’s the impression I get.

I suspect this varies from a completion framework to another; e.g. the resultant order seems to differ between Ivy and Vertico. I guess it can be further modified by histsave and other modes (prescient?) that influence the order if you have any turned on.

4

nobiot, thanks for confirming. You are right that different frameworks show (slightly) different order of results. I see differences between selectrum and vertico.

It’s not a big issue, but it will be good to have a definitive way to get results in modification time order.

5

Given that different completion frameworks seem to modify the completion-table, it would be specific to your completion framework of choice.

I think you would need to study how your completion and your config do it in detail.

I am reasonably happy with how mine is at the moment.

6

Yes, I’ll try out the various completion frameworks. On a quick look, ivy-mode listing seems closest to file-mtime. Thanks.