Make search smarter? about org-rifle HOT 5 OPEN

Org has no built-in mechanism for tracking how often headlines are visited. org-recent-headings does that, but whether a heading is considered visited depends on whether certain functions are called; see its customization options. Theoretically helm-org-rifle could consult org-recent-headings-list to sort entries, but that would be slow when there are a lot of results.

There is no existing mechanism by which relevance could be calculated. Trying to do so would reduce performance, but you're welcome to propose such a mechanism, as it could be useful at times.

from org-rifle.

I have the same idea that there could be an optional (controlled by a customize option) bias for entries which are often selected. For example, if I search for "java" and I have lots of matches, but there are several matches which I often select for the search "java" then rfile could offer those first. Org rifle itself could keep a file storing which entries are selected by the user for which searches and using this file it could list those items first if the user does the same search again.

from org-rifle.

@nerton That request is essentially already provided by using a Helm command that combines the helm-org-ql source with the org-recent-headings source, like so:

(use-package helm-org-ql
  :after org-ql
  :config
  (defun ap/helm-org-ql-and-recent-headings ()
    "Search `org-recent-headings', and `org-directory' files with `org-ql'"
    (interactive)
    (helm :sources (list helm-source-org-recent-headings
                         (helm-org-ql-source (org-ql-search-directories-files)
                                             :name " Org Directory Files")))))

Of course, you should have org-recent-headings installed and activated. Then headings that you've recently viewed that match the query (at least, in the heading text) will be shown first. It works well for me.

from org-rifle.

Of course, you should have org-recent-headings installed and activated. Then headings that you've recently viewed that match the query (at least, in the heading text) will be shown first. It works well for me.

"at least, in the heading text". That is the key. org-rifle matches the whole entry, so if I search for "inflation" for example, then it lists entries even when "inflation" is in the body. If org-rifle supported order by usage frequency then the earlier selected item could be listed first when I search for "inflation" even if the match is in the body.

from org-rifle.

That could be useful, but to be clear, I don't plan to add a usage-frequency feature to this package. If there are certain headings that you access frequently, org-recent-headings is designed for that express purpose. If there's a certain keyword in the body of an entry that leads you to it, you should probably add it to the heading or tag the entry with it. Or you could bookmark it with org-bookmark-heading (and add Helm's bookmarks source to your Helm command).

If you haven't tried org-ql yet, please do. It's like the "next-generation" of org-rifle.

from org-rifle.