org-diary VS todo.txt

* etc

So with that in mind I have an emacs org-file, which has a standard set of headers which are inserted in a single file, beneath today's date.

I use the following emacs package to make that easy to manage:

* https://github.com/skx/org-diary

With that in place I get something like this automatically:

      * 31/08/2022

I use a single file, with standard headers, with a new entry for each day. I use `org-diary` to manage that:

https://github.com/skx/org-diary

Every morning I run `org-diary-new-entry` which inserts a new block. At the end of the day I commit this to a git repository and push it away for safety. I've got a work-log/journal going back a couple of years at this point.

It would be awesome to have an option to sync to/from a text file in the todo.txt format. This is a plain text format for tasks which can be read by different apps on different platforms.

For this project: Make a todo.txt file in the root. Don't go overboard, just note the tasks as you realize them as "(B) Add Audio System". Break them down into components when you realize tasks will take more than one sit-down, "(A) Put AudioDefs into an array \n (B) Load each of the filedata into a stack". Personally, I use (A) for "This is on the schedule", (B) "Do this today", etc.

Another way is to use the todo.txt approach and add context tags like "@work" to the text of the task, and then filter the big Tasks list by searching for that context tag.

todo.txt on linux (format definition, tool -- available in most package repos also I think, though the name is not always the same!)

Privat mittlerweile nach Todo.txt-Aufbau https://github.com/todotxt/todo.txt/blob/master/description.svg

Actually, it's org-mode. But for the rest of us non-Emacs users, there's todo.txt:

https://github.com/todotxt/todo.txt

Otherwise, maybe go old school and use a todo.txt type workflow?