3 ms·

I'm curious as to how to implement this ? I mean, i currently put everything that needs doing into org-mode, clock in on the task when i'm working on it, and c

I'm curious as to how to implement this ? I mean, i currently put everything that needs doing into org-mode, clock in on the task when i'm working on it, and clock out when i'm done. Mark the task completed, and archive done tasks daily to an archive file. I guess that's the limit of my daily "todo" activities. It's mostly in point form "x needs doing", "request confirmation from x", "send status on project x to y". If i'd have to do it in a "daily file" i have no idea how to structure it. Todo'ish lists probably wouldn't work. They're either done or they're not. I guess it would have to be more like "short stories".

pcnix 6y ago
Might I suggest checking out org-journal? It's a natural extension of the org-mode way of things, and integrates quite well with the agenda too.
bcrosby95 6y ago
I went the opposite direction as you may be going: from daily markdown files, to 1 giant org mode file where the date is the top header, to 1 giant org mode file where my TODOs etc. are the top header. I think what works best depends upon how you plan to use them and what your workflow looks like. But I have tended to find the "1 giant file" is a better fit for me.