"t-" : A less-than-minimal task list "manager"
penzba.co.uk
penzba.co.uk
But "t" didn't run on my very old, stick-it-in-the-corner-and-occasionally-play machine (which only has Python 2.2.1) so I spent a happy hour putting this together, more-or-less at random.
I'm finding it's helping, but maybe that will only be till the novelty wears off.
Thanks for sharing it, these one-hour happy projects are the most fun to read and hack
I found an odd thing: I added twice a task with the same name, and the random number is the same, i.e. t- test -> 098f test, doing it again results in 098f test twice. I guess the "random" number is just some hash applied to the string, but this means that let's say, if I put three "do the laundry" (3 washmachines, for example), when I remove them all three will be deleted at once.
More here: http://blog.jerodsanto.net/2010/12/minimally-awesome-todos/
function todone() { sed -i -e "/$*/s/.*/\o033[9m&\o033[0m/" $TODO; }
edit: gnome-terminal supports this, but it seems xterm and putty do notAlso, putting these two lines before your import will make it run without complaint on Python 2.6.x:
import warnings
warnings.filterwarnings('ignore', 'the md5 module is deprecated')<fx: shrug> YMMV.
- delete a task 'dd' -> two keystrokes, no need to remember some arbitrary id
- select a task 'gg' -> go to line number
- add new task 'o' -> one keystroke
- add a bash alias 't' for "vim ~/.tasks" and you have the power of vim and still need fewer keystrokes to manage tasks ;)
Still, why i would use such a tool is far beyond me, honestly.
I can understand using some advanced taskmanagers with GUI or a textfile, but i don't understand the benefits of t ;)But you're convinced it's of no value to you, and that's cool. Don't use it.
But if you haven't tried it, can you really be sure?
Anyway, you are right, i haven't tried it, and i probably won't because my workflow and taskmanagement works different (and already works for me).
Everyone should use what suits him best.
my workflow and taskmanagement works different
(and already works for me). Everyone should
use what suits him best.
Absolutely. This is just another option for those that aren't yet happy with what they do or have.(It feels wrong describing extra features. I wanted fewer, not more)
It also runs without requiring a recent version of Python. It doesn't use "with", "OptParse", or the ternary "if". Therefore it runs on my really old machine sitting in the corner that I can't be bothered upgrading. That's where I do a lot of "Hmm - I'll just try this" hacking.
My home internet is down, so I don't have the latest version handy. This shows I should keep things in github.
I'll post an older version from my laptop here now, and follow up later with the latest if I remember.
This is missing key functionality:
- 'run' command which spoon feeds you a random selection of the tasks
However, you can start it, and see the schema, and that direction it's headed in.
function count_tasks {
~/bin/t | wc -l | sed -e's/ *//' 2> /dev/null | sed -e s/0//'
}
export PS1="\h:\W\$(parse_git_branch)\$(count_tasks) $ "i.e script and to do list are one and the same.
Dev-Todo http://swapoff.org/DevTodo
If you use e.g. zsh then maybe you also like this for your rc file.
If you need anything beyond the basics
you might want to look at todo.txt or
TaskWarrior instead. They’re great tools
with lots of bells and whistles.
In contrast, t (and therefore t-) does almost nothing. Instead, to make your task list prettier, do some work!http://stevelosh.com/projects/t/#it-does-the-simplest-thing-...
Otherwise it's just "task add something", "task list", "task done something".
And if you do find yourself wanting to use those "bells and whistles", they're just a man page away.
It just doesn't look like what I want. I like being able to just go in and edit the task list. I like being able to use the Unix philosophy and have sorting, prioritising, selecting, and counting in a pipeline.
I don't want much, and t- gives me what I want.