uuid: - value: c1bf1868-5c9b-4ab9-8565-3e6340c8fb65 langcode: - value: en type: - target_id: daily_email target_type: node_type target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7 revision_timestamp: - value: '2025-05-11T08:59:58+00:00' revision_uid: - target_type: user target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849 revision_log: { } status: - value: true uid: - target_type: user target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849 title: - value: 'Plain text TODOs' created: - value: '2025-05-07T00:00:00+00:00' changed: - value: '2025-05-11T08:59:58+00:00' promote: - value: false sticky: - value: false default_langcode: - value: true revision_translation_affected: - value: true path: - alias: /daily/2025/05/07/st langcode: en body: - value: |
In January, I wrote about using plain text files for to-do lists instead of larger and more complex project management tools.
I found an example of this in the code repository for st, the simple terminal from suckless.org.
They have a TODO.html file which is a plain text list of todo tasks.
There are a lot of examples on GitHub, too.
Something I like in st's file is this command:
grep -nE 'XXX|TODO' st.c
This finds TODO comments in the st.c file so those can be included.
format: full_html processed: |In January, I wrote about using plain text files for to-do lists instead of larger and more complex project management tools.
I found an example of this in the code repository for st, the simple terminal from suckless.org.
They have a TODO.html file which is a plain text list of todo tasks.
There are a lot of examples on GitHub, too.
Something I like in st's file is this command:
grep -nE 'XXX|TODO' st.c
This finds TODO comments in the st.c file so those can be included.
summary: null field_daily_email_cta: { }