emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Agenda fails to parse time interval like 23:00-29:00 [9.1.9 (release_9.1.9-65-g5e4542 @ /home/yantar92/.emacs.d/straight/build/org/)]
Date: Sun, 08 Dec 2019 00:24:31 +0800	[thread overview]
Message-ID: <87a784hznk.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87pnh0un8u.fsf@nicolasgoaziou.fr>

> What makes you think the time interval above is correct? I would also
> expect an error from that time specification.

I also thought that it is incorrect (and posted a bug report since it is 
what is produced by typing 11pm+6 in org-read-date). 
However, I got a reply that 23:00-29:00 is a valid time interval
format [1].

Best,
Ihor

[1] https://lists.gnu.org/archive/html/emacs-orgmode/2019-07/msg00039.html 


Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> 'Ihor Radchenko' <yantar92@gmail.com> writes:
>
>> I have one scheduled item like the following:
>>
>> * test
>> <2019-12-05 Thu 23:00-29:00>
>>
>> This kind of item fails to be parsed by agenda because of incorrect
>> treatment of 23:00-29:00 time interval
>
> What makes you think the time interval above is correct? I would also
> expect an error from that time specification.
>
> Regards,
>
> -- 
> Nicolas Goaziou

  reply	other threads:[~2019-12-07 16:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02  2:49 Bug: Agenda fails to parse time interval like 23:00-29:00 [9.1.9 (release_9.1.9-65-g5e4542 @ /home/yantar92/.emacs.d/straight/build/org/)] 'Ihor Radchenko'
2019-12-07 16:14 ` Nicolas Goaziou
2019-12-07 16:24   ` Ihor Radchenko [this message]
2019-12-07 16:35   ` Ihor Radchenko

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=87a784hznk.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me \
    --to=yantar92@gmail.com \
    --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).