todo.txt VS rich

It would be awesome to have an option to sync to/from a text file in the todo.txt format. This is a plain text format for tasks which can be read by different apps on different platforms.

For this project: Make a todo.txt file in the root. Don't go overboard, just note the tasks as you realize them as "(B) Add Audio System". Break them down into components when you realize tasks will take more than one sit-down, "(A) Put AudioDefs into an array \n (B) Load each of the filedata into a stack". Personally, I use (A) for "This is on the schedule", (B) "Do this today", etc.

Another way is to use the todo.txt approach and add context tags like "@work" to the text of the task, and then filter the big Tasks list by searching for that context tag.

todo.txt on linux (format definition, tool -- available in most package repos also I think, though the name is not always the same!)

Privat mittlerweile nach Todo.txt-Aufbau https://github.com/todotxt/todo.txt/blob/master/description.svg

Actually, it's org-mode. But for the rest of us non-Emacs users, there's todo.txt:

https://github.com/todotxt/todo.txt

Otherwise, maybe go old school and use a todo.txt type workflow?

There is an open issue [1] on GitHub to make it more modular and get rid of markdown and syntax highlighting but I have no hope for rich to get more minimal.

[1]: https://github.com/Textualize/rich/issues/2277

I hope he doesn't mind, but the creator of Rich and Textualize is a good guy, and Scottish: https://www.willmcgugan.com/about/

https://www.textualize.io/

https://github.com/Textualize/rich

They keep getting improved error messaging and this is one of my favorite features. But I'd love if we could get some real rich text. Idk if anyone else uses rich, but it has infected all my programs now. Not just to print with colors, but because it makes debugging so much easier. Not just print(f"{var=}") but the handler[0,1]. Color is so important to these types of things and so is formatting. Plus, the progress bars are nice and have almost completely replaced tqdm for me[2]. They're just easier and prettier.

[0] https://rich.readthedocs.io/en/stable/logging.html

[1] Try this example: https://github.com/Textualize/rich/blob/master/examples/exce...

[2] Side note: does anyone know how to get these properly working when using DDP with pytorch? I get flickering when using this and I think it is actually down to a pytorch issue and how they're handling their loggers and flushing the screen. I know pytorch doesn't want to depend on rich, but hey, pip uses rich so why shouldn't everyone?

colors.crumb extends Crumb with basic terminal styling functions and RGB, HEX, ANSI conversion functions. It is in the realm of JavaScript's chalk and Python's rich but slightly more functional 😉.

I am working on a new python project and one of the first things I added was https://github.com/Textualize/rich because of how easy it is to make things look good in the terminal.

I am not rewriting anything but I'd love to have a library like `rich` in Rust: https://github.com/textualize/rich

Add some cool-looking stuff to your output with rich.

You might consider taking inspiration from the rich module. In particular, I like how rich supports inline color theming which seems much more cumbersome in your framework, requiring the use of context managers as well as familiarity with how your framework structures color objects. Other than that though, I'm impressed!