At the end of each day, I do a quick review of what’s on the agenda for tomorrow, like appointments, and then look at my task list to pull in things I think I’ll have time to do between the appointments. For this purpose, my daily journal template has a block called “Tomorrow:” in it every day.
Is there a way to bring the previous day’s “Tomorrow:” block (and its children) into each new day’s journal template automatically? This seems like quite a meta question, making a template based on the previous day’s use of itself, but it’d save me the step of scrolling through all the rest of whatever happened the previous day to grab the block reference and embed it in my new day’s journal manually.
In case it helps, I’ll try to create an example:
How my completed day’s journal currently looks:
What went well?
Good thing
Good thing
Good thing
What could’ve gone better?
Bad thing
Bad thing
Tomorrow:
Appt at 0900
TODO 1
TODO 2
Appt at 1400
How I’d like it to look:
PLAN:
Tomorrow:
Appt at 0900
TODO 1
TODO 2
Appt at 1400
What went well? (etc.)
I definitely do NOT want to embed the whole previous day. That’s very specifically what I’m trying to avoid. I just want to embed the previous day’s plan at the top of the current day’s journal so I have the agenda from the day before right at the top, ready to go. It’s fine with me if the “Tomorrow:” heading from the previous day still shows up on the current day, but it’d be even nicer if it didn’t.
My head gets twisted in pretzels when I try to think of how I could do this, but hopefully someone can help!
Replying because I’d like this feature also. There might be a plug-in that does this. There are several todo management plug-ins in the library. If I actually saw one, I didn’t install it because at the time I didn’t want to add any more to my set up. Haven’t returned to look.
I found it! Daily TODO
Did you already look at this one?
The author says it’s very specific to their workflow. It might not do what you want. But it seems close without my analysis.
Good Luck.
Hmm, yes, this is somewhat close to what I want! It does several other things I don’t want, though, so I might have to see if I can figure out how to alter the code (only minimal experience with this, and not familiar almost at all with regex, which is in the code).
For example, I often create new tasks on a specific date because that’s when I thought of them, but I didn’t actually expect/want to do them on that date, and I don’t want them to move forward. I just want them to stay there.
I also have one category of tasks that MUST be left open, and on their specific day, because I only process those specific tasks once every two weeks in a specific meeting, and it’s important that they stay with their date reference. They’re “TODO,” because they need to be brought up in that meeting, but it’s also important that I keep the record of when each one came up. I have a query on the meeting’s page that relies on the journal date to tell me when the issue came up.
I’ll also have to see how it handles DOING tasks, because I use that status quite a bit in my current workflow.
I might be able to delete all the code except the part that processes the tasks under underlined headings, though. I could certainly turn my “Tomorrow” heading into an underlined heading, and then just not have the rest of the code.
I’m afraid there’s way too much code in there that I don’t even know how to read, though, some of which looks like it might migrate EVERY undone TODO from EVERY past journal to the present day, which I very much want to avoid, so it’s going to take quite awhile before I can look into this, learn enough about the language of this code, and guess how to edit it for what I need.