I have been playing more with (and getting frustrated by) the parser - for example, the ability to assign tasks to a particular parent folder/task using the -tofld and -to parameters (which appear not to required a space).
It seems clear that where you are matching to a name (folder, task or flag) you can enter the first part of the name as the parameter and it will match to this. However, will it match to another part of the name? I am now using tags on my task names for ones that I want to jump to a lot (eg #sapr for my Prospects folder which is in the Sales folder) (in the absence of named bookmarks) and this works quite well with MLO's find functionality. At the moment, I put these at the end of the Task name (eg 'Prospects [#sapr]'). I have tried using these tags as parser parameters (eg -tofld#sapr) but can't get them to work consistently. (I think I got it to work once but now it doesn't work at all). So the question is - does the name matching in the parser work on any of the Task name or just on the beginning. And if it only works on the beginning, could it be made to work on any part? Aside: my preferred approach for this would be to allow named bookmarks for tasks and to provide a dynamic matching facility both on search and in RTE - ie you signal in someway that you are entering a bookmark name and MLO then starts to present a list of matching tasks (because I can't hold all these names in my head) -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Richard C Sent: 09 June 2010 10:56 PM To: MyLifeOrganized Subject: [MLO] Re: Parser idiosyncrasies I remain intrigued - why do I have to leave a space after the -d parameter but not after the -fl parameter? On Apr 15, 7:41 pm, Richard C <[email protected]> wrote: > Butwhat's the logic behind this - why do I need to leave a space > between -d and Todaybutnotbetween -fl and Key? What are the rules > for the other flags. Why can't they be consistent. I am a > moderately experienced IT person with experience using using command > line driven software - if I struggled to make them work, I would > imagine many others would find them as problematic (ifnotmore so) > > I did read the documentation (bad habit of mine!)and found nothing > about the rules for leaving spaces. Incidentally, there is a typo - > refernce to the -lf parameter rather than -flflag(just to prove that > I did read them!) > > Re delicious links - they do reflect my professional interest - IT > consultant working in theNotFor Profit sector. > > On Apr 15, 4:20 pm, pottster <[email protected]> wrote: > > > > > Hi Richard, > > > > So the rule seems to be "don't leave a space between -fl and the name of the > > >flagbutdo leave a space between -d and thedateand then remember to put > > > thedateparameter at the end." > > > Pretty much, except the order doesn't matter if you if just put the > > first word of the keyflagname (it's the space that causes the > > problem) e.g. <Msg text> -d Today -flKey works fine - fewer key > > presses as well ;-). Just remember to make the first word of your > > flags unique in some way. > > > Have you checked out the updated User Guide on the website for 3.5.0? > > It includes a run down on the new parsing functionality. > > > Regards, > > Ken > > > PS thanks for the Delicious links. Look forward to having a look at > > those. > > > On Apr 15, 11:53 am, "Richard Collings" <[email protected]> > > wrote: > > > > Occasionally I try to use the parser in the Rapid Task entry screen and each > > > time I give up because I can't get it to work. I have just spent a bit more > > > time on this today and I think this illustrates my point. > > > > I am trying to enter a task and assign it aDueDateof Today and to assign > > > theflagflag"Key task" with the following results > > > >Assignswrongflag"Requested" and nodate > > > <Msg text> -fl Key Task -d Today > > > <Msg text> -d Today -fl Key Task > > > >AssignsFlagbutnotDueDate > > > <Msg text> -dToday -flKey Task > > > <Msg text> -d Today -flKey Task > > > <Msg text> -flKey Task -dToday > > > <Msg text> -dToday -fl Key Task > > > >Assignsboth > > > <Msg text> -flKey Task -d Today > > > > There were others that didn't work as wellbutthis was before I > > > systematically started to capture what was working and what wasnotworking > > > > So the rule seems to be "don't leave a space between -fl and the name of the > > >flagbutdo leave a space between -d and thedateand then remember to put > > > thedateparameter at the end." > > > > Is this working as expected? > > > > I have to say that I would have thought most people would have given up long > > > before I did. > > > > Richard > > > > Interesting stuff (possibly): http://delicious.com/richardcollings > > > > <mailto:[email protected]> - Hide quoted text - > > > - Show quoted text -- Hide quoted text - > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mylifeorganized?hl=en. -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mylifeorganized?hl=en.
