[feature request] Add option to capture a new heading right from helm-org-ql buffer

[yantar92]

Similar to org-roam's search behaviour, it might be a useful addition to allow creating a new heading when interactive helm-org-ql's query fails.

I imagine something like in the attached screenshot:

WDYT?

[alphapapa]

It's an interesting idea, and one I think I've seen in other places. I'm not necessarily opposed to it, but I don't know exactly how it would work. Ideally I guess there would be some kind of "common" Helm actions list for Org headings that we could use, rather than implementing this specifically and only in helm-org-ql.

[yantar92]

... Ideally I guess there would be some kind of "common" Helm actions list for Org headings that we could use, rather than implementing this specifically and only in `helm-org-ql`.

I guess "create new heading" as a helm action can be an option, though I had something similar to helm-mini in mind. In helm-mini, there is helm-source-buffer-not-found source used to create a new buffer. Similarly, helm-org-ql can use something like the following: (cl-defun yant/helm-org-ql-agenda-files (arg) "Like `helm-org-ql-agenda-files', but also allow creating a new heading." (interactive "P") (let ((files (if arg (org-agenda-files t t) (org-agenda-files t)))) (helm :prompt (format "Query (boolean and): ") :sources (list (helm-org-ql-source files :name "Org Agenda Files") (helm-build-sync-source "Create new" :candidates (lambda () (if (string-empty-p helm-pattern) (list "New note") (list (format "New note: \"%s\"" (string-clean-whitespace helm-pattern))))) :match #'identity :match-dynamic t :nohighlight t :action '(("New note" . (lambda (_) (let ((helm-org-ql-default-title helm-pattern)) (org-capture nil "N")))))))))) Of course, the "new note" source can be also added to other helm-org-ql commands. The problem with the above code is hard-coded capture template. I am not sure what would be the best way to deal with it, especially how to set the default template.

[alphapapa]

I see, well, that's an interesting idea. I feel like it might be a bit out-of-scope for org-ql to include by default, but I'm not strictly against it.