Dwight - which popup are you talking about? The popup that appears when you start typing in the Context field (in the Properties pane on the right of the scree) is irritatingly small on my (4K) screen, but I cant find a way to enlarge it. If you meant just the Alt-L popup, thanks I have adjusted.
Christoph - have you considered putting Context tags into Hotkeys? They are a great way to remove as well as add tags. Personally I only ever use the Context field to add new Context - a rare event. I prefer hotkeys or to right-click on the Context column which I have added to the main area of the screen. SRhyse - I have read but I disagree with much of what you say. I have no stomach for further ideological debate with you however. Daniel - Just to say that the reality is that we users quickly invest a vast amount of our TIME in learning, customising and entering data into their task management software e.g. MLO. If you value your time, time equates to money and given how much customisation is possible (and arguably required!) to set up MLO, most MLO users are huge investors in MLO and the actual money price paid for the software soon becomes irrelevant in comparison. Moreover, unless you actually want to Spring Clean occasionally, the personal cost of jumping ship is likely to be significant. On Thursday, January 11, 2018 at 10:42:52 PM UTC, daniel wrote: > > I like your response. I have no animosity of people wanting things to be > a certain way. I may not understand it, and certainly not from their > perspective, but I do not mind them wanting it. I'd like to have personal > programming done for me also. However I do get agitated when some really > bash the program, probably more so for just it being one more stream of > negativity into my day than anything else. However I am a MLO loyalist. I > think some are just unwilling to bend or adapt. I understand it, I manage > 43 people in a multi-million dollar business. I am sometimes the fire > breathing personification of I want things the way I want them and since I > am paying you to provide me with a service its unacceptable that I cannot > have what i want! (that is directed at vendors, but every once in a while > an employee as well ) However the scale is much different. This is piece > of software that cost me less than 100 dollars US and requires pocket > change to upkeep. I do not have the right to demand more from Andrey and > CO. He offered a product, I purchased, I received the value of what I > bought. I'm happy with it, I want more people to love it and use it. > Beyond that...to the ones that do not like it, that is ok, wish you the > best, hope something else works out for you. In the meantime I'm going > back to work. > > On Thu, Jan 11, 2018 at 5:24 PM, SRhyse <srh...@gmail.com <javascript:>> > wrote: > >> The original language of GTD is loose enough that ‘context’ is just a >> distinction you make between different types of tasks to make your lists >> smaller and easier so you don’t feel overwhelmed, and to put similar things >> in the same space so you can do one after another if they have similar >> requirements to get down. The way the David Allen company has continued >> coaching it is entirely in line with that too. ‘Waiting For’ and ‘Someday >> Maybe’ are both used as contexts to them. I’m not concerned with what is or >> isn’t GTD, but if you’re going to talk about GTD, it’s always been that >> way, and they’ve always been open about that. If you’re not using entirely >> separate flat lists, ‘context’ is just a tag meant to organize data on >> another level that isn’t hierarchy. Plenty of people now use energy levels >> and time as contexts as mentioned. >> >> I personal don’t find it hard to enter contexts because I keep their >> names short, and their numbers few. You can have a context that for you >> means “things I would like to considering doing someday,” or “things I >> would only like to do when I’m tired,” but you don’t have to name them in >> that way. I’ve varied over the years, but I tag things I’m waiting for with >> ‘@w’ or just a ‘w’. If it’s something that won’t take any brain power to >> do, I consider it shallow work and use @s or s. All of my contexts work >> like that, and I don’t have too many because that usually serves as ways of >> hiding things so I don’t see them, which is the opposite of effectively >> managing and making decisions on them. I also don’t do ‘someday’ in >> contexts because anything not on a todo view or with a context is a pipe >> dream, and if it isn’t, I’ll just tag it and have it show up when it should >> based on date or sequence or dependency. I’ve actually found it better to >> store that stuff outside of MLO because at that point it’s just reference >> notes and past thinking, though MLO’s Markdown support and potential for a >> ‘note’ designation may bring it back in for me. Having contexts parse out >> as things are typed is simple in this case, as is clicking on a context to >> assign it to one or more tasks. Moving it under an existing task with that >> context also works, and in the very off chance it doesn’t, you just change >> the context of that task. >> >> And to Dwight: I wouldn’t consider you trying to discuss things with >> people as defensive. If people bring up issues and requests on a public >> forum, discussing them is kind of the point. That is the only point of a >> forum. That is what a forum is. Discussing something doesn’t mean blindly >> agreeing with it or leaving it unexamined. If someone said they’d like MLO >> to have a field for ‘dogs’ in it, the best response probably wouldn’t be >> “sure thing! We’ll add it to the list,” particularly not if that user went >> on for 4 or more years saying MLO was silly and unacceptable and stupidly >> clumsy for not having implemented the ‘dog’ feature that made no sense and >> had no real utility, and was requested by a user that by their own >> admission no longer used the program. If that user wasn’t willing to take >> half a second to tag something with ‘dog’, they also apparently don’t value >> their desired ‘dog’ functionality very much. Bending the development team >> over backwards to add in dog-like functionality seems like a waste of >> resources, and trying to discuss that first would appear to be the more >> fruitful course of action than burning more time and money. >> >> Best, >> >> S >> >> -- >> You received this message because you are subscribed to the Google Groups >> "MyLifeOrganized" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to mylifeorganiz...@googlegroups.com <javascript:>. >> To post to this group, send email to mylifeo...@googlegroups.com >> <javascript:>. >> Visit this group at https://groups.google.com/group/mylifeorganized. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/mylifeorganized/cf096155-7c67-4a47-a36d-4d28cee090af%40googlegroups.com >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To unsubscribe from this group and stop receiving emails from it, send an email to mylifeorganized+unsubscr...@googlegroups.com. To post to this group, send email to mylifeorganized@googlegroups.com. Visit this group at https://groups.google.com/group/mylifeorganized. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/b2a814b4-0cad-4a31-9390-a3f81509f3f7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
