Our great sponsors
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
-
organice
An implementation of Org mode without the dependency of Emacs - built for mobile and desktop browsers
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
logseq
A local-first, non-linear, outliner notebook for organizing and sharing your personal knowledge base. Use it to organize your todo list, to write your journals, or to record your unique life.
For reference, this is the discussion around subitems / nesting: https://github.com/jotaen/xit/discussions/2
As mentioned in that ticket, I’m still reluctant to add this to the [x]it! file specification. On the one hand it seems like an obvious and useful feature, but on the other hand it’s unfortunately pretty difficult to implement in tooling. For example, I tried to add experimental support for nested subitems in the Sublime Text plugin, but I eventually had to give up, just because the syntax highlighting engine is so limited in regards to recursion. It’s the same – or much worse – for other editors.
At the end of the day, I feel that it doesn’t help to add such a feature to the file format, if tools then cannot deal with it properly. Right now, the spec is so simple that it can be implemented in maybe a day or so. I see a great deal of value in keeping the hurdle for tool creators small. So it’s a pretty tricky balancing act.
I am almost using this format for my markdown todo app written in Ruby:
https://github.com/coezbek/rodo
Differences:
I use unicode symbols such as ⌛ or for paused or priority items.
I use dash for obsolete/canceled items. I find this more in line with bullet journal which inspired the development of Rodo.
I do use markdown bullet lists.
For a standalone CLI, I still prefer https://github.com/todotxt/todo.txt-cli - probably because there are Android and iOS clients for it, and it's based around a bash script.
For vim, I just use vim-wiki, which is a superset of this functionality.
Of course, looking through this thread, there's lots of different options. Which is cool.
Taskwarrior uses a pain text format and is excellent. It's my daily driver todo list. https://taskwarrior.org
An online site that does task warrior sync - https://inthe.am
