clach04

Compatibility with gocryptfs would be useful in of itself.

@Vesnyx were you able to spend time on this?

Cross reference to https://github.com/schollz/croc/issues/247 (which links to an Android implementation)

OwnTone - see https://github.com/basings/selfhosted-music-overview/issues/141

ldap support would be neat, could be used with https://github.com/nitnelave/lldap/ or OpenLDAP, etc.

The current SVG https://github.com/todotxt/todo.txt/blob/8d19d67227f0a695303c29159bd7bb5c77a21fdb/description.svg makes clear that key/values can be anywhere in or after the description, but adding to the end is a good convention. I suspect this wasn't present...

Great idea! Quick copy and paste of some existing examples ## extract of first example in readme from https://github.com/todotxt/todo.txt#incomplete-tasks-3-format-rules (A) Thank Mom for the meatballs @phone (B) Schedule Goodwill pickup...

@jaimegarza I suspect you've opened this issue against the wrong project, what tool are you seeing this in?

Android SimpleTask, from https://github.com/mpcjanssen/simpletask-android/blob/master/app/src/main/assets/index.en.md#extensions (as of 2022-09-11): Simpletask supports the following todo.txt extensions: - Due date as `due:YYYY-MM-DD` - Start/threshold date as `t:YYYY-MM-DD` - Recurrence with `rec:\+?[0-9]+[dwmyb]` as described [here](https://github.com/bram85/topydo/wiki/Recurrence)...

Seen [ttps://gitter.im/todotxt/Lobby?at=6284470aeaf3267f8566d9e3](https://gitter.im/todotxt/Lobby?at=6284470aeaf3267f8566d9e3): `id:` `blocks:1` I've also seen `p:1` to show the parent (for sub-tasks).