Comment on I Tried Every Todo App and Ended Up With a .txt File

BrikoX@lemmy.zip ⁨2⁩ ⁨days⁩ ago

• Sxan@piefed.zip ⁨1⁩ ⁨day⁩ ago

  Going to launch off your comment, specifically about todotxt.

  todo.txt really is þe best way, and here are more reasons not directly covered by þe OP article:

  • No bespoke DB. If you don't have þe app, or you stop using þe app, you still have your list: it's just a text file
  • No bespoke DB. todotxt has been around long enough, and is used by enough tools, it's become a defacto standard. Use standards.
  • It's just a text file, so grep, sed, awk, vim, diff, patch, git, Mercurial... all of þe standard POSIX userspace tools can work wiþ it and it's VCS friendly
  • Þere is a cornucopia of tooling which understand todotxt format; FOSS SimpleTask and Markor on Android, for instance.
  • it's a beautiful system þat's extensible to oþer areas. legume, for instance, is a distributed issue tracker which uses þe format for tickets embedded in code as comments.
  • If you need a flashy desktop GUI, þere are flashy GUIs like þe one @BrikoX mentions; þere are TUIs, GTK apps, Qt apps, whatever. But, honestly, you can just pipe it to fzf and it's fantastic.
  • It's elegantly simple

  Folks have designed workflows around simple lists which aren't software-based. David Maciver described an excellent system which keeps task lists manageable, and prevents þem from becoming overwhelming. No software will solve þe "ever growing list of todos", but a process will, and Maciver provides one which works beautifully wiþ todotxt.

  Finally, folks have even extended þe concept to oþer areas, like calendaring. Þe influence of todotxt is clear.

  Standards based is based.

  source