From: Justin Silverman <jsilve24@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Intervals that include day of the week recently causing error in org-agenda
Date: Mon, 10 May 2021 22:44:34 -0400 [thread overview]
Message-ID: <af51654f-56e3-f995-c23d-0f248452aaca@gmail.com> (raw)
First -- apologies if duplicate post (I tried to send email with M-X
org-submit-bug-report but I don't think it sent and
https://updates.orgmode.org/ gives 502 bad gateway so I am not sure I
can even check if it sent)
Until yesterday a time stamp of the following form was accepted and
didn't cause problems in org-agenda.
<2021-04-29 Thu 10:35-11:50>
However, as of a recent update (that I downloaded yesterday) I notice
that this causes an error
org-duration-to-minutes: Invalid duration format: #("10:35-11:50" 0 11
(fontified nil line-prefix #(" " 0 2 (face org-indent)) wrap-prefix
#(" " 0 2 (face org-indent)) org-category "cal-gmail"))
SPC ESC is undefined
What fixes this is if I remove the Weekday in the timestamp so it reads:
<2021-04-29 10:35-11:50>
I would say this is a bug with other libraries (that create timestamps
with days of the week, but I notice that base org-mode creates these
timestamps (e.g., with C-c C-d 2021-04-29 10:35-11:50 C-c C-c). In
other words, if this is the correct new default behavior / formatting
requirement for org-agenda then I would expect that the
deadline/scheduled/timestamp entering function (sorry not sure of the
correct name for things like C-c C-s and C-c C-d) would abide by this
convention.
That said, I would like the old way that was slightly less rigorous
(e.g., allowing days of the week) as some other libraries (e.g.,
org-gcal) use that format.
Thank you!
Justin
next reply other threads:[~2021-05-11 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 2:44 Justin Silverman [this message]
2021-05-11 15:19 ` Intervals that include day of the week recently causing error in org-agenda Nicolas Goaziou
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=af51654f-56e3-f995-c23d-0f248452aaca@gmail.com \
--to=jsilve24@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).