input parsing : new task -s1/30/17at8am -d1/30/17at9:30am rmd10min

[george]

Hi

In this input parsing string everything works(start date and time and end date and time) except the reminder. I want the reminder 10 before due at 9:20 but it is not what i am getting. 

new task -s1/30/17at8am -d1/30/17at9:30am rmd10min

What is the error in this entry?

Thanks!

[Stéph]

I just tried this. The parsing section in the help file says that I should be able to write new task -s1/30/17at8am -d1/30/17at9:30am rmd 10min in advance, but it still only recognizes this as setting a reminder for 10 minutes from the current time. I think you may have found a bug there. I'll pass it to the other beta testers.

Thanks,

Stéphane

[george]

Thank You. I spent quite some time typing this over and over.. hoping for correct result. 

If this gets fixed it would help a lot in my quest to reduce mouse usage.  

[Ray Emerson]

George - 

  This was a little tricky! Below is a screen capture with several different examples. I believe the "new task 6" syntax is what you're after.

  
Cheers.

Ray

[Stéph]

Thanks for spotting that a space after the -d switch gets the reminder working, Ray.  However, we then run into a separate problem with the parser, as shown by your new task 4:  If you put a space after the -d or -s switches, then MLO won't recognize both the start and due dates.  So, we're currently stuck with being able to enter start and due dates (if you don't include the space) or just the due and reminder dates (if you do include the space). This is a bug - but it's a bug in a standard library function, so I think it will be a while before it can be fixed for MLO.

[george]

Actually this seem to work

new task -s2/2/17at10am -d 2/2/17at2pm rmd 9am

new task -s2/3/17at3pm -d 2/3/17at5pm rmd10min

So it seems like space before -d seem to be the key element here. if there is space before both -s and -d then dates seem to get messed up. Either way guess the parsing need to be smoothed out. 

Thanks Ray & Stéph