Am Tue, 22 Sep 2015 21:24:59 +0200 schrieb Nicolas Goaziou <m...@nicolasgoaziou.fr>:
> Hello, > > Detlef Steuer <detlef.ste...@gmx.de> writes: > > > Met this funny bug in the morning. > > > > (orgmode version: git from today) > > > > Given the file > > > > * Testappointment > > SCHEDULED: <2015-09-21 Mo 23:00-23:55> > > > > If I now shift the *starttime* using shift-uparrow > > the *endtime* goes to 24:00, 24:05 etc. > > > > If I keep shifting the *endtime* goes from > > 24:55 to 24:00 again. > > > > The *starttime* correctly rolls over to 0:00 . > > Fixed, somewhat. Thank you. > > Note that it can still produce meaningless timestamps, e.g., > > <2015-09-21 Mo 23:00-23:55> => <2015-09-21 Mo 23:05-00:00> > > but at least, it is predictable. > Thx! I don`t consider that time-stamp meaningless. At least for humans :-) Using the context you know it´t 0:00 the next day. I doubt it were better to split a time intervall at midnight into a regular time span, say <2015-09-21 Mo 23:00-23:55> => (+ 5min) <2015-09-21 Mo 23:05>--<2015-09-22 Di 00:00> Not worth the trouble I´d say. The time span given in an intervall HH:MM-HH:MM always is < 24h and endtime > startime, so even a program could interpret it correctly. As always, thx for fixing so fast! Detlef > > Regards, > -- Dr. Detlef Steuer Helmut-Schmidt-Universität Fakultät WiSo Holstenhofweg 85 22043 Hamburg Tel: 040/6541-2819 mail: ste...@hsu-hh.de