From: Garjola Dindi <email@example.com>
Subject: Re: Invalid duration format error with active timestamp
Date: Wed, 19 May 2021 21:40:34 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On Tue 18-May-2021 at 23:23:39 +02, Rainer Hansen
> Hi Garjola,
> I had the same problem.
> I fixed it by downloading manually the last working version of Org from
> i.e. https://orgmode.org/elpa/org-20210503.tar
> and manually stored the extracted directory into my elpa directory,
> /home/garjola/.emacs.d/elpa/ in your case.
> After restarting Emacs Org agenda worked fine again.
> I hope that helps.
Thanks for the tip. I finally got the update via the package manager
before having the time to test your solution.
And org works great as always!
> Garjola Dindi <email@example.com> writes:
>> On Mon 17-May-2021 at 16:01:25 +02, Nicolas Goaziou
>> <firstname.lastname@example.org> wrote:
>>> Garjola Dindi <email@example.com> writes:
>>>> I am using the most recent elpa version of org
>>>> 9.4.5 (9.4.5-93-gbc857b-elpa @
>>>> /home/garjola/.emacs.d/elpa/org-20210510/) with emacs master branch.
>>>> Since updating org yesterday, when I use a timestamp like
>>>> | <2021-05-17 Mon 10:00-11:00>
>>>> building the agenda fails with this backtrace:
>>>> | Debugger entered--Lisp error: (error "Invalid duration format:
>>>> | #(\"10:00-11:00\" 0 5 (font...")
>>> This was fixed a few days ago.
>>> Since Org in ELPA is updated every Monday, you need to update it again
>>> (later?) today to get the fix.
>> Thanks for your answer. I've been impatiently refreshing the packages
>> since yesterday, but I don't see any new version of org.
>> I am using
>> Is this still correct? Just wondering, since I understood that some
>> things are changing in org packaging and distribution.
>> Thanks for your great work!
prev parent reply other threads:[~2021-05-19 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 12:07 Invalid duration format error with active timestamp Garjola Dindi
2021-05-17 14:01 ` Nicolas Goaziou
2021-05-18 17:42 ` Garjola Dindi
2021-05-18 21:23 ` Rainer Hansen
2021-05-19 19:40 ` Garjola Dindi [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).