Tags might improve that but I’m not sure yet. It’s not that much time to do the context switching and works well. Since we have time constraints of doing chores if we have a lot of things to do we may blow off the less critical ones if more important ones take more time than expected. Right now I just check the local town context on the drive to the city (I am a passenger in the car, don’t do this and drive) and change the context to the city and back again if we don’t get the action done while there. (Our bank is local and only has a branch in the 2 local towns, for example) That way I could see errands that can be done in either place easily. My only use case is to flag the local town errands I can also do in the city with both places and vice versa. The first custom perspective I have is called Projects. I’m also following a lot of the foundational instructions in that guide like using the and viewing projects as Remaining. While it’s pretty clear that I can only get a lot of things at the further away city (which requires a whole day as we’ve got 3+ hours of drive time to get to and from) while there I can also do most of the errands from the local towns. The Forecast Perspective is built into OmniFocus and you can learn more about that in the official GTD set up guide. For example otask -l c:email will show all contexts containing a fuzzy match. The far away towns are where we do major shopping once a month. I took the good parts of it, concentrated on OmniFocus and converted it to. 1 is the 2 closest towns, sort of the run to town places less than 10 miles away and one is 2 towns that are a 1.5 hour drive to get there. I have a single action list Errands and I have 2 locations as contexts. I can’t really think of an instance where I needed a tag with a single exception. I’m not a tagger by nature, so I’m not even sure I will use tags at all. I’m curious what other people are thinking about doing.
0 kommentar(er)
