Re: Clock time implied as 00:00

[Nick Dokos <nicholas.dokos@hp.com>]

François Pinard <pinard@iro.umontreal.ca> wrote:

> Hi, Org people.
> 
> This morning, I just noticed this line:
> 
> CLOCK: [2011-12-29 jeu 9:30]--[2011-12-29 jeu 11:44] => 11:44
> 
> because of the strange 11:44 total.  My error is clear, as I wrote 9:30
> instead of 09:30.  Correcting it gives a move reasonable total:
> 
> CLOCK: [2011-12-29 jeu 09:30]--[2011-12-29 jeu 11:44] =>  2:14
> 
> Yet, forgetting a leading 0 is an easy mistake (I know I should not make
> mistakes!), and then, maybe (I'm not sure) Org mode could deliver
> unexpected or misleading statistics out of a silent error.  Not such a
> problem for me, yet it could have become one if I missed it.
> 
> Would it be reasonable to suggest that Org mode be more lenient about
> missing leading zeroes?
> 

IMO, yes. This looks like a bug in org-parse-time-string which is supposed
to be an optimized parse-time-string, but look:

,----
| (setq ts "2011-12-29 Thu 2:11")
| "2011-12-29 Thu 2:11"
| 
| (parse-time-string ts)
| (0 11 2 29 12 2011 4 nil nil)
| (org-parse-time-string ts)
| (0 0 0 29 12 2011 nil nil nil)
`----

Nick

> François
> 
> P.S. I wish every one is enjoying the Festive Times!
> 
>