From: Detlef Steuer <detlef.steuer@gmx.de>
To: emacs-orgmode@gnu.org
Cc: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: funny bug if shifting scheduled items
Date: Wed, 23 Sep 2015 11:16:52 +0200 [thread overview]
Message-ID: <20150923111652.15f963d8@gaia> (raw)
In-Reply-To: <87fv26b6k4.fsf@nicolasgoaziou.fr>
Am Tue, 22 Sep 2015 21:24:59 +0200
schrieb Nicolas Goaziou <mail@nicolasgoaziou.fr>:
> Hello,
>
> Detlef Steuer <detlef.steuer@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: steuer@hsu-hh.de
prev parent reply other threads:[~2015-09-23 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 7:11 funny bug if shifting scheduled items Detlef Steuer
2015-09-22 19:24 ` Nicolas Goaziou
2015-09-23 9:16 ` Detlef Steuer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150923111652.15f963d8@gaia \
--to=detlef.steuer@gmx.de \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).