could 'am' and 'pm' be smarter?
davekaminski says:
It's 1:25pm CDT Sunday where I am. In the web-interface input I typed
" at 2:30"
and the site dutifully told me that it had registered an event that was to occur at 2:30am Monday--not at all what I wanted. I know the system probably defaults to 'am' when neither am nor pm is specified, but couldn't the default just be the next occurrence of the desired time point? That seems like it would make a lot more sense.
Thanks.
" at 2:30"
and the site dutifully told me that it had registered an event that was to occur at 2:30am Monday--not at all what I wanted. I know the system probably defaults to 'am' when neither am nor pm is specified, but couldn't the default just be the next occurrence of the desired time point? That seems like it would make a lot more sense.
Thanks.
davekaminski says:
of course that's supposed to be "<task> at 2:30"
I didn't preview before I posted.
I didn't preview before I posted.