3 ms·

I don't see a difference between that and a plain textfile..

by buster 16y ago

RiderOfGiraffes 16y ago
That's what I thought when I first read about "t". Then I tried it, and it really does feel different. <fx: shrug> YMMV.
Groxx 16y ago
Plain text files you have to select an editor to open it in, modify it, and save it. More steps than necessary, a command line interface really is ideal for something super-simple like this. Though it could be made as / might just be a handful of bash scripts wrapping around `cat`, not everyone has the know-how or desire to make such a thing, but many can use it.
- buster 16y ago
  But i have to open a terminal to use t. I argue that using vim is more efficient then t: - 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 ;)
  - RiderOfGiraffes 16y ago
    You don't always have a terminal open? I find that odd. Personally I always have a terminal open - it's where I do most of my work - so to add a task it's just typing it in, preceeded by "t-". I don't have to remember arbitrary IDs, they are listed. 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?
    - buster 16y ago
      Actually i always have several terminals and several desktops open. I think my workflow would be to open a terminal on the "PIM" desktop and have vim running there. 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.
      - RiderOfGiraffes 16y ago
        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.

I don't see a difference between that and a plain textfile..

by buster 16y ago

I don't see a difference between that and a plain textfile..

That's what I thought when I first read about "t". Then I tried it, and it really does feel different. <fx: shrug> YMMV.

Groxx 16y ago

Plain text files you have to select an editor to open it in, modify it, and save it. More steps than necessary, a command line interface really is ideal for something super-simple like this. Though it could be made as / might just be a handful of bash scripts wrapping around `cat`, not everyone has the know-how or desire to make such a thing, but many can use it.

buster 16y ago
But i have to open a terminal to use t. I argue that using vim is more efficient then t: - 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 ;)
- RiderOfGiraffes 16y ago
  You don't always have a terminal open? I find that odd. Personally I always have a terminal open - it's where I do most of my work - so to add a task it's just typing it in, preceeded by "t-". I don't have to remember arbitrary IDs, they are listed. 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?
  - buster 16y ago
    Actually i always have several terminals and several desktops open. I think my workflow would be to open a terminal on the "PIM" desktop and have vim running there. 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.
    - RiderOfGiraffes 16y ago
      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.