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

Nick Anderson

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?

@awws perhaps someday. I spend way more time using my system than tweaking it. It often takes me quite a while to integrate changes. I have yet to publish things I have written about my history with org-mode and emacs and how I org.

@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.

@nickanderson That approach looks cool.

How do you deal with your TODOs then?

*Not* scattering them doesn't automatically improve things, I can tell :) I refile my TODOs in a handful of org files, but it's still way too many to make the TODO agenda work for me at all. I would have to separate "to-actually-do" from "this-is-doable-in-theory" (which both are different from regular org content headings) 🤔

I can only imagine it's even more the case with spreading TODOs through org-roam

@ctietze In reality, currently I don't have anything or really try to wrangle them. I schedule things in my calendar if I need to box time and I don't yet try to pull my calendar in to agenda either. I simply have a daily log that contains my work for the day and where I clock time. It links to other various things. When something becomes important enough and or interesting enough I work on it.

@ctietze I don't even have many todos anymore. It was an ever growing list that just worked against me psychologically. But I still want to use agaend, it seems so powerful. Using agenda based on files that contain nodes with created property from some period seems like it could help both with parse time and horizon. Probably usually I don't care about the three year old todo that isn't done because if it were important it would have resurfaced and I would have done it.

@ctietze in fact using that method I found several todos that I had done, but never marked them. But likely I had logged that work in a daily file probably the same day or next day around the created time.

@nickanderson Hmm I see! FWIW, my approach doesn't work for me 'psychologically' either. I usually work on some (creative) task during the day and complete implicit or explicit todo's along the way, but usually never sit down and check which TODO I should tackle next