Quote:
|
Originally Posted by coconino
If my understanding of contexts is correct—that it is "what you can do, where you are, with the tools available"—then "Waiting for" is not a true context and asking the context system in OmniFocus to handle waiting-fors is to knock a hole in the hard wall of that definition.
|
Let's go to the source: "You'll probably find it works best to keep this 'Waiting For' list close at hand, in the same system as your own 'Next Actions' reminder lists. The responsibility for the next step may bounce back an dforth many times before a project is finished." So sayeth the David, p. 149.
So, no, "Waiting for" is not a context. In the book, it's never referred to "@waiting for," in the sense that "@office" or "@computer" is noted. But when it comes down to it, we're just talking about lists. Whether there's an @ sign before the name isn't really important, and treating the list as another context allows a level of customization (separate WF lists for personal/professional, for example) that would be lost if "waiting for" were formalized as a feature.