* Bug: SCHEDULED's end time wrong [9.5.2 (9.5.2-gfbff08 @ /Users/liutos/.emacs.d/elpa/org-9.5.2/)]
@ 2022-02-19 14:20 Liutos
2022-02-20 6:49 ` Ihor Radchenko
0 siblings, 1 reply; 7+ messages in thread
From: Liutos @ 2022-02-19 14:20 UTC (permalink / raw)
To: emacs-orgmode
[-- Attachment #1: Type: text/plain, Size: 881 bytes --]
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
------------------------------------------------------------------------
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.
Emacs : GNU Emacs 27.1 (build 1, x86_64-apple-darwin18.7.0, NS
appkit-1671.60 Version 10.14.6 (Build 18G95))
of 2020-08-12
Package: Org mode version 9.5.2 (9.5.2-gfbff08 @
/Users/liutos/.emacs.d/elpa/org-9.5.2/)
[-- Attachment #2: Type: text/html, Size: 1049 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: Bug: SCHEDULED's end time wrong [9.5.2 (9.5.2-gfbff08 @ /Users/liutos/.emacs.d/elpa/org-9.5.2/)]
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-21 15:22 ` Liutos
0 siblings, 2 replies; 7+ messages in thread
From: Ihor Radchenko @ 2022-02-20 6:49 UTC (permalink / raw)
To: Liutos; +Cc: emacs-orgmode
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Bug: SCHEDULED's end time wrong [9.5.2 (9.5.2-gfbff08 @ /Users/liutos/.emacs.d/elpa/org-9.5.2/)]
2022-02-20 6:49 ` Ihor Radchenko
@ 2022-02-20 13:50 ` Greg Minshall
2022-02-20 14:05 ` Ihor Radchenko
2022-02-21 15:22 ` Liutos
1 sibling, 1 reply; 7+ messages in thread
From: Greg Minshall @ 2022-02-20 13:50 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: emacs-orgmode, Liutos
Ihor,
i tried Liutos' example, and ended up with
> * a simple entry
> SCHEDULED: <2022-02-20 Sun 23:59-24:29>
i think it is the "-24:29" that is of concern.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Bug: SCHEDULED's end time wrong [9.5.2 (9.5.2-gfbff08 @ /Users/liutos/.emacs.d/elpa/org-9.5.2/)]
2022-02-20 6:49 ` Ihor Radchenko
2022-02-20 13:50 ` Greg Minshall
@ 2022-02-21 15:22 ` Liutos
2022-02-21 15:36 ` Ihor Radchenko
1 sibling, 1 reply; 7+ messages in thread
From: Liutos @ 2022-02-21 15:22 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: emacs-orgmode
[-- 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 --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Bug: SCHEDULED's end time wrong [9.5.2 (9.5.2-gfbff08 @ /Users/liutos/.emacs.d/elpa/org-9.5.2/)]
2022-02-21 15:22 ` Liutos
@ 2022-02-21 15:36 ` Ihor Radchenko
0 siblings, 0 replies; 7+ messages in thread
From: Ihor Radchenko @ 2022-02-21 15:36 UTC (permalink / raw)
To: Liutos; +Cc: emacs-orgmode
Liutos <mat.liutos@gmail.com> writes:
> 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.
Thanks for the additional information!
I am unable to reproduce the issue on my side.
Can you try to reproduce the error on latest main and bugfix starting
from emacs -Q? See https://orgmode.org/manual/Feedback.html#Feedback
Best,
Ihor
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2022-02-21 15:38 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2022-02-21 15:36 ` Ihor Radchenko
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).