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 <r...@rcollings.co.uk> 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 <kenwarren...@googlemail.com> 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" <rich...@rcollings.co.uk> > > 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:rich...@rcollings.co.uk> - 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 mylifeorgani...@googlegroups.com. To unsubscribe from this group, send email to mylifeorganized+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/mylifeorganized?hl=en.
