fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

10K
active users

This is pretty great, set org-agenda-files based on node properties in the org-roam database. I am so scatter brained tossing TODOs all over the place and this just might be the path towards sanity.

@nickanderson Interesting! The idea being you have a streamlined list of todos w/o parsing all files??

Is that your goal here?

@awws Yes, exactly! Long ago Agenda piqued my interest, made me think that I could put these TODOs in any org file anywhere on my file-system. But, in practice it was painful to have all files part of the agenda list, and directory structures weren't a great fit for me either, still pulling in too much or too little. But, with org-roam-db-query I think I can get a reasonable set of files for Agenda to parse with low maintenance.

@awws It can also allow me a time based cliff where for example I didn't get that TODO done in 3 months, just fall out of scope and stop. Clearly it wasn't that important, or if it is, it will certainly come up again. I'm excited about it. Time will tell if it changes my workflow I guess.

@nickanderson I have a complex system which archives all files that have no active TODOs every few months to an .org_archive extension which is visible to search but not to the agenda-files build.

So, very curious how your db querying goes.

Blog post?

Nick Anderson

@awws I typically use archive tag but leave things where they are. Org-roam has helped me avoid my previous problem with multi-megabyte individual files. I've not yet gotten agenda to stick in my workflow but I keep trying from time to time.