Marty Oehme
a4bbb0ed3a
Following this blogpost: https://eshapard.github.io/code/a-separate-taskwarrior-configuration-for-ideas.html I think it is a really good idea to try this out. At first I was collecting ideas in my regular taskwarrior repository -- this was no good as every task list was flooded by somedays and maybes which would never leave. But I still wanted to have a nice repository to collect all my ideas in. So, the second strategy was to have one big (markdown) file which would simply collect all my ideas. But now I was doubling and tripling them up because the list was so long, and it was more of a chore to find where to put everything than just a quick 'idea add'. This may be the best of both worlds: making use of the nice interface to a task database using the full strength of taskwarrior querying, without cluttering up my main task repository. The workflow is exactly as with regular taskwarrior, only the executable is not called `task` (or `t` in my case) but `idea`. So you e.g. add an idea with `idea add`, or query all diy ideas with `idea +diy`. Just like regular taskwarrior. |
||
|---|---|---|
| .. | ||
| taskrc | ||