From fba68d779ce549f6b252c136942efad3fb4da2cd Mon Sep 17 00:00:00 2001
From: Oliver Davies <oliver@oliverdavies.uk>
Date: Thu, 8 May 2025 08:00:00 +0100
Subject: [PATCH] Add daily email for 07/05/25

---
 source/_daily_emails/2025-05-07.md | 32 ++++++++++++++++++++++++++++++
 1 file changed, 32 insertions(+)
 create mode 100644 source/_daily_emails/2025-05-07.md

diff --git a/source/_daily_emails/2025-05-07.md b/source/_daily_emails/2025-05-07.md
new file mode 100644
index 000000000..bfaa89f2c
--- /dev/null
+++ b/source/_daily_emails/2025-05-07.md
@@ -0,0 +1,32 @@
+---
+title: Plain text TODOs
+date: 2025-05-07
+permalink: daily/2025/05/07/st
+tags:
+  - software-development
+cta: ~
+snippet: |
+  A while ago, I wrote how I use plain text files for my project to-do lists. Today, I found an example whilst looking at an open source project repository.
+---
+
+
+In January, I wrote about [using plain text files for to-do lists][3] 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][1].
+
+They have a [TODO.html file][0] which is a plain text list of todo tasks.
+
+There are [a lot of examples on GitHub][2], too.
+
+Something I like in st's file is this command:
+
+```plain
+grep -nE 'XXX|TODO' st.c
+```
+
+This finds TODO comments in the st.c file so those can be included.
+
+[0]: https://git.suckless.org/st/file/TODO.html
+[1]: https://st.suckless.org
+[2]: https://github.com/search?q=path%3Atodo.txt+OR+path%3Atodo.md+OR+path%3Atodo.html&type=code
+[3]: {{site.url}}/daily/2025/01/03/todotxt