Quote:
Originally Posted by Rauchbier
Why is this not possible with contexts? Because for me a context is a place or a work condition like "office", "home" or "phone". But what about "Jack"? I could meet him in the office or call him on the phone. It does not make sense to me to have different office:Jack and phone:Jack contexts since it often does not matter if I speak to him on the phone or in the office.
|
I wouldn't do it that way, either - 99% of the time, the method I'm using to have the conversation is irrelevant. In the rare cases where there's something that I want to discuss in person, I note that in the action.
My setup works like this: I have an "omni" parent context; one of the subcontexts is 'people', with each of the folks I work with underneath. Ditto for friends and other the other high-level context categories I use.
Tasks relating to a given person get filed to the person's context; I check that context when I'm talking to them regardless of the method I'm using.
My 'phone' context doesn't have any subcontexts - it's only used for calls to relatively anonymous folks, businesses, etcetera. Things I'm extremely unlikely to accomplish in person.