rodo VS grit

I wrote a small Ruby TUI which works like this called Rodo (Ruby Todos). Pressing CTRL+t will get you a new Todo list (it's just markdown) at the top of a file.

https://github.com/coezbek/rodo

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.

Nice! I also have this pain of the file losing shape quickly. My take is to have a a CLI tool to "carry over" all todos which aren't solved into a new heading. This way the old/resolved items are moved to the back/lower in the file.

I call it Rodo (Todos in Ruby): https://github.com/coezbek/rodo

It uses Markdown for syntax.

Definitely true, but sometimes the lack of sane tooling makes it harder to follow rituals. I used to use the same format as the OP in a text editor, but struggled with the daily grind of copying items around and carrying over todos from the last day. Paper is much better for this, but messy (even with scanning).

In the end I wrote a small tool to assist with starting each day with a blank journal and all remaining items from the last day. Syntax is primarily markdown.

https://github.com/coezbek/rodo

I have recently developed my own terminal-based UI for day journalling and todo/task tracking [1] in markdown files because I was sick of rearranging todos in other tools and just needed something which provides a standard template for each day (journal, high priority, todos of the day).

The main advantage is that you can "migrate" all unfinished todos to a new page/day and thus get a clean start each day. This idea comes from bullet journalling.

To get it done I had to dig a bit into ncurses, which turned out more interesting than I thought. For instance, Windows Terminal just gained support for bracketed paste a couple of months ago and my tool supports it.

Long term I would like to add generated views (for instance: last year this time one of your highlights was...) and support recurring tasks to be inserted into he daily log.

[1] https://github.com/coezbek/rodo

Stack: Ruby, Curses, Markdown

This is cool, but the killer feature I'm looking for is a UI to accomplish the functionality of grit https://github.com/climech/grit. Grit itself isn't particularly functional, but its write-up in the readme hasn't been fully realized by any task tracking software (as far as I'm aware).

*

By specifying order through indentation, we've now created a DAG for what needs to be done, in what order, with the most actionable tasks having the largest indentation. This is how I organize my plaintext to-do files, but afaict no todo list software is able to handle this gracefully- with the exception of grit, which is more of an experiment (but the readme is incredibly well written and describes DAG problem to a tee).

https://github.com/climech/grit

Does anyone know if org-mode handles complex trees? All the examples I've found online were trivial (i.e. one task deep)

Seems like it uses sqlite. Presumably it's trivial to sync using whatever file sync tool you want (Dropbox, or whatever) as long as you're fine without concurrent editing. For that you'd need application support or a more amenable data structure.

https://github.com/climech/grit/blob/master/db/db.go