seems that most of the functionality here can be replicated with basic shell commands:
t add "blah" == echo "blah" >> Todo.txt
t ls @search == grep @search Todo.txt
so all this does is ... color-code task priorities - meh
That's what shell scripts do in general, they automate things you could have done yourself with a bit more typing. With a todo list I feel it is absolutely vital that there is as little friction as possible. You don't want the process of recording and tracking what you have to do to distract you from actually doing it!
Plus how long would it take you to accidentally type "echo blah > todo.txt" instead of "echo blah >> todo.txt". I'm thinking a few days for me :)
This is all academic of course, everyone should be using org-mode for todo lists. What do you mean you don't have Emacs running all the time?? ;)
Agree with the generalization. But from the screencast, there is no indication this does anything other than alias basic shell commands. I'd recommend the author screencast something that the average shell user won't look at and wonder why even bother. At least the source code reveals something a little more useful.
I've been using todo.sh for a couple years now, and this is a feature, not a bug. Since everything is in line-oriented text files, I can just use standard shell commands (or a text editor!) when it's more convenient. But the script makes it slightly easier and faster to do very common or complex operations.
so all this does is ... color-code task priorities - meh