From: Tim Loderhose <email@example.com>
To: Ihor Radchenko <firstname.lastname@example.org>
Cc: Jarmo Hurri <email@example.com>, firstname.lastname@example.org
Subject: Re: Stable 9.5: invalid function (date date)
Date: Mon, 29 Nov 2021 13:52:57 +0100 [thread overview]
Message-ID: <CAAYD+1Hsh9_FNGqeFmPrAn0SCnBwZDpam1U4fpf=bioaNWBLzw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
I refactored my emacs config and it appears like the problem is gone now.
(I was just using use-package, but there may have been some bit loading org
Thanks for the pointer in any case!
On Thu, Nov 25, 2021 at 11:09 AM Ihor Radchenko <email@example.com> wrote:
> Tim Loderhose <firstname.lastname@example.org> writes:
> > Hi,
> > I am also getting this error. It's fixable only by re-installing org
> from a
> > emacs -q, I assumed because files on the agenda file list are visited
> > before org is fully installed?
> > Unfortunately, this also occurs with a fresh install of Emacs
> > (re-installing all packages), but I'm not sure why. I'd assumed it's
> > because of the agenda file list, but that doesn't exist at that point.
> > I will try these days to get a minimal config to reproduce the issue, and
> > will respond again.
> This is a known problem for users loading Org early in their config and
> using non-standard package managers (like straight.el). See
> In the linked thread we are also discussing some ways to address this on
> Org side, but no good solution yet. Patches are welcome.
[-- Attachment #2: Type: text/html, Size: 1901 bytes --]
next prev parent reply other threads:[~2021-11-29 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 6:51 Stable 9.5: invalid function (date date) Jarmo Hurri
2021-10-02 7:23 ` Ihor Radchenko
2021-10-03 3:34 ` Jarmo Hurri
2021-11-25 9:53 ` Tim Loderhose
2021-11-25 10:10 ` Ihor Radchenko
2021-11-29 12:52 ` Tim Loderhose [this message]
2021-11-30 20:18 ` Simon Butler
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).