Thank you for sharing it. The problem with this approach is that (a) you can’t plug it into existing pile of notes and (b) messing up with your customize file leads to broken agenda.
This post motivated me to share how I approach this problem that I am using for a month already and super happy about it’s performance. You can read detailed description on my blog. The code is available as a GitHub Gist.
TL;DR - in the before-save-hook current buffer is traversed for existence of any TODO entires and Project tag is either added or removed from #+ROAM_TAGS property. Now, org-agenda is adviced before to set the value of org-agenda-files to the list of files with Project tag (quieried from db, which is enourmously fast).
There is also a snipped to use for migration. This way all required information is always there, in your files and can be easily reconstructed. That being said, proposed solution can be easily adapted to dynamic-agenda-files approach.
This code snippet for collecting files with todos has greatly impacted my workflow! Thanks for sharing.
I am just trying to figure out how this would work with org-roam V2. ROAM_TAGS have been dropped and from the code it seems that FILETAGS will only get stored in the database if there are headline nodes with ID that inherit the tag. And even if this would work, every todo in the agenda woud be tagged with “Project”, adding visual clutter.
Have you adapted this for the new version already? Would it make sense to use a note that is being linked to by every file that contains todos and then query the database for backlinks?
I cannot contribute to @cool_ran’s script, but wanted to respond to two points you commented about V2.
I have been using V2 every day for work for a couple of weeks now; FILETAG just works without headline nodes.
Most of my org files do not have headlines. I use FILETAG as a category, like Meeting, Reference, etc. No issue.
I think this is largely related to how you use/customise agenda (I do not show any tags in my agenda view; I just use them as search keys)… You could also look to control how file-level tags get inherited by the looks of this Org documentation.
To limit tag inheritance to specific tags, or to turn it off entirely, use the variables org-use-tag-inheritance and org-tags-exclude-from-inheritance .
I don’t use these variables so I cannot be 100% certain, but it’s probably worth looking into.
Thanks for the hint to org-use-tag-inheritance, this keeps the agenda view clean as I do not use tags for other purposes than marking files with todos inside.
After some time testing, this does not work for me. Filetags are somehow not consistently added to the database. It worked for the some daily files with tasks and for some the caching function does not add the filetags to the db entry.
However, the modified code from @d12frosted works flawlessly in adding the tags and retrieving them from the db.
Has anyone else used filetags successfully with V2?
This is a very interesting idea for workflow that might work for me well.
I’m currently trying to make the code work at least partially with org-roam v2.
What I want is to add to org-agenda-files files with “Project” tag. This is implemented by those two functions:
(defun vulpea-project-files ()
"Return a list of note files containing Project tag."
(seq-map
#'car
(org-roam-db-query
[:select file
:from tags
:where (like tags (quote "%\"Project\"%"))])))
(defun vulpea-agenda-files-update (&rest _)
"Update the value of `org-agenda-files'."
(setq org-agenda-files (vulpea-project-files)))
When I run vulpea-project-files function, I receive the following error: EmacSQL had an unhandled condition: "no such column: file"
I tried to investigate the structure of org-roam.db with .schema command to understand which column name should I use. Here is what I got:
Slight mod that I had to figure out to keep specific files in the agenda. As the functions does’t append, it overwrites. Please Educate me of a better way to do this…
Sure, the method I described simply overrides whatever you had in org-agenda-files. If you wish it to always contain some values you have two options:
A method you described with a separate list of agenda files that is concatenated with project files. Works well even for notes outside org-roam-directory.
Tag these files with an appropriate tag, so that vulpea-project-files result contains them. Doesn’t work if files in question are outside of org-roam-directory (like your calendar files).
I think these two functions should be enough. Though I must ask - why do you want to do it? DB gets updated much more often than your list of agenda files gets modified. At least in my experience. So I would get unnecessary reads from DB. And this might lead to performance degradation (though this is mere speculation).
The code is fantastic—thanks d12frosted for sharing it.
I’d like to supplement it with a function that checks whether each file in the org-roam directory was modified in the last n days, so that org-agenda lists both files with a TODO element and files modified recently. Unfortunately, I am not able to create such a function. The shell command find "path-to-org-roam-directory" -mtime -n -ls finds the files modified in the past n days, and perhaps one could pass its output to shell-command-to-string to generate a list of the relevant directories, but I’m not sure how to do that, or whether a different approach is more appropriate. Any help would be appreciated.
DB gets updated much more often than your list of agenda files gets modified. At least in my experience. So I would get unnecessary reads from DB. And this might lead to performance degradation (though this is mere speculation).