oliverdavies.uk/content/node.c1bf1868-5c9b-4ab9-8565-3e6340c8fb65.json

91 lines
3.4 KiB
JSON
Raw Normal View History

2025-05-11 07:15:45 +01:00
{
"uuid": [
{
2025-05-11 09:40:11 +01:00
"value": "c1bf1868-5c9b-4ab9-8565-3e6340c8fb65"
2025-05-11 07:15:45 +01:00
}
],
"langcode": [
{
"value": "en"
}
],
"type": [
{
"target_id": "daily_email",
"target_type": "node_type",
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
}
],
"revision_timestamp": [
{
2025-05-11 09:40:11 +01:00
"value": "2025-05-11T08:59:58+00:00"
2025-05-11 07:15:45 +01: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": [
{
2025-05-11 09:40:11 +01:00
"value": "2025-05-11T08:59:58+00:00"
2025-05-11 07:15:45 +01: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": [
{
2025-05-30 02:14:32 +01:00
"value": "\n <p>In January, I wrote about <a href=\"\/daily\/2025\/01\/03\/todotxt\">using plain text files for to-do lists<\/a> instead of larger and more complex project management tools.<\/p>\n\n<p>I found an example of this in the code repository for st, <a href=\"https:\/\/st.suckless.org\">the simple terminal from suckless.org<\/a>.<\/p>\n\n<p>They have a <a href=\"https:\/\/git.suckless.org\/st\/file\/TODO.html\">TODO.html file<\/a> which is a plain text list of todo tasks.<\/p>\n\n<p>There are <a href=\"https:\/\/github.com\/search?q=path%3Atodo.txt+OR+path%3Atodo.md+OR+path%3Atodo.html&amp;type=code\">a lot of examples on GitHub<\/a>, too.<\/p>\n\n<p>Something I like in st's file is this command:<\/p>\n\n<pre><code class=\"plain\">grep -nE 'XXX|TODO' st.c\n<\/code><\/pre>\n\n<p>This finds TODO comments in the st.c file so those can be included.<\/p>\n\n ",
2025-05-11 07:15:45 +01:00
"format": "full_html",
2025-05-30 02:14:32 +01:00
"processed": "\n <p>In January, I wrote about <a href=\"http:\/\/default\/daily\/2025\/01\/03\/todotxt\">using plain text files for to-do lists<\/a> instead of larger and more complex project management tools.<\/p>\n\n<p>I found an example of this in the code repository for st, <a href=\"https:\/\/st.suckless.org\">the simple terminal from suckless.org<\/a>.<\/p>\n\n<p>They have a <a href=\"https:\/\/git.suckless.org\/st\/file\/TODO.html\">TODO.html file<\/a> which is a plain text list of todo tasks.<\/p>\n\n<p>There are <a href=\"https:\/\/github.com\/search?q=path%3Atodo.txt+OR+path%3Atodo.md+OR+path%3Atodo.html&amp;type=code\">a lot of examples on GitHub<\/a>, too.<\/p>\n\n<p>Something I like in st's file is this command:<\/p>\n\n<pre><code class=\"plain\">grep -nE 'XXX|TODO' st.c\n<\/code><\/pre>\n\n<p>This finds TODO comments in the st.c file so those can be included.<\/p>\n\n ",
2025-05-11 07:15:45 +01:00
"summary": null
}
]
}