From: Liutos <mat.liutos@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: SCHEDULED's end time wrong [9.5.2 (9.5.2-gfbff08 @ /Users/liutos/.emacs.d/elpa/org-9.5.2/)]
Date: Mon, 21 Feb 2022 23:22:29 +0800 [thread overview]
Message-ID: <CAAxQUKaFS5yi8V36P9jOzEQVB5vESVemGu30MJ0KMM14qMO6ag@mail.gmail.com> (raw)
In-Reply-To: <87ee3ykp6w.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
Sorry for missing the error's detail. Here it is
```
org-duration-to-minutes: Invalid duration format: "+0:29"
```
I seen this message from my Emacs' *Messages* buffer after I invoke
org-agenda. And the *Org Agenda* buffer is empty except a simple title.
Ihor Radchenko <yantar92@gmail.com> 于2022年2月20日周日 14:49写道：
> Liutos <mat.liutos@gmail.com> writes:
>
> > Assume there is an entry as simple as following
> >
> > * a simple entry
> >
> > Move the cursor on the entry, then press C-c C-s for setting its
> > SCHEDULED property. Then type `23:59+0:30` and press Enter key. The
> > resulting SCHEDULED property will be an ill-formed value such as
> > `<2022-02-19 Sat 23:59-24:29>`, which will cause error in org agenda.
>
> Could you clarify what kind of error is triggered?
> <2022-02-19 Sat 23:59-24:29> is a perfectly valid date range format,
> which should be handled by org-agenda without issues.
>
> Best,
> Ihor
>
--
Liutos Love Linux LaTeX Lisp Ling
我的GitHub主页：https://github.com/Liutos
[-- Attachment #2: Type: text/html, Size: 1694 bytes --]
next prev parent reply other threads:[~2022-02-21 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-19 14:20 Bug: SCHEDULED's end time wrong [9.5.2 (9.5.2-gfbff08 @ /Users/liutos/.emacs.d/elpa/org-9.5.2/)] Liutos
2022-02-20 6:49 ` Ihor Radchenko
2022-02-20 13:50 ` Greg Minshall
2022-02-20 14:05 ` Ihor Radchenko
2022-02-20 14:14 ` Greg Minshall
2022-02-21 15:22 ` Liutos [this message]
2022-02-21 15:36 ` 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=CAAxQUKaFS5yi8V36P9jOzEQVB5vESVemGu30MJ0KMM14qMO6ag@mail.gmail.com \
--to=mat.liutos@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@gmail.com \
/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).