[Vimoutliner] VimOutliner as a task manager?

[Steve Litt]

On Friday 02 November 2007 18:03, Scott Scriven wrote:
> * Steve Litt <slitt at troubleshooters.com> wrote:
> > I'm finding something interesting as I put @this and @that --
> > there's a hierarchy of @this and thats.
> >
> > For instance, license goes in @wallet, which goes in @jeans
> >
> > plane_reservation goes in @folder1 which goes in @carryon
>
> This sounds like you might be over-doing it a little.  Have you
> passed the point where the outline costs more time than it saves?

Heck no!!!

One of my biggest problems in past packs is I knew something was packed, but 
not where, so I had to go looking to make sure. The ability to create packing 
locations and even nest them is a tremendous help for me.
>
> If I recall correctly, one of the principles of Getting Things
> Done is that you shouldn't write down more than necessary --
> avoid overhead where possible.  Too much accounting is
> counter-productive.

Absolutely. Having nested locations is just enough, not too much.

>
> The @context markup is generally used for filtering by vague
> categories, such as things you can do at home, things you can do
> at work, things to do while particular people are around, things
> to do at the grocery store, etc.  The idea is that you can, when
> you're looking for something to do, quickly get a list of things
> you *can* do in a given context.  I can't do my laundry while I'm
> at work, and the @context notation keeps it off my list when it's
> not relevant.

NOW I'm beginning to understand the purpose. The preceding paragraph is worth 
its weight in gold. Thanks!

>
> Some people like to make it more specific, such as organizing
> grocery items by which aisle they're in, but I've found even that
> tends to be more effort than it's worth.

Yeah, I think by isle is more than its worth, but organizing by store is a 
huge time and gas saver.

Thanks

SteveT

Steve Litt
Author: Universal Troubleshooting Process books and courseware
http://www.troubleshooters.com/