From: Robert Thorpe <firstname.lastname@example.org>
To: Stephen Berman <email@example.com>
Cc: firstname.lastname@example.org, email@example.com
Subject: bug#51815: 27.2; Strange interaction between Org and Diary
Date: Mon, 15 Nov 2021 03:45:11 +0000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (message from Stephen Berman on Sat, 13 Nov 2021 20:47:22 +0100)
Stephen Berman <firstname.lastname@example.org> writes:
> On Sat, 13 Nov 2021 21:29:03 +0200 Eli Zaretskii <email@example.com> wrote:
>>> From: Robert Thorpe <firstname.lastname@example.org>
>>> Date: Sat, 13 Nov 2021 19:16:16 +0000
>>> I use Org mode but I also use the normal calendar and diary.
>>> This has an unwanted effect if I open an org file. After org has been
>>> started the calendar no longer functions as expected. If I press "i d"
>>> then it fails to insert an entry in the diary file. A warning in
>>> *Messages* says:
>>> "command-execute: Wrong type argument: commandp, org-agenda-diary-entry"
>>> I don't use org-agenda, BTW.
>>> To clarify there are two conditions that are needed to see this
>>> 1) Org-mode has been started in the Emacs session.
>>> It does not happen if org-mode hasn't been started (e.g. by opening an
>>> org file in another buffer).
>>> 2) Org-mode must be started first before calendar.
>>> If calendar is started first and org-mode is started second then the
>>> calendar works.
>> Which version of Org are you using? the one that came with Emacs 27.2
>> or something else?
> This is bug#48199, which was fixed in Org bundled with Emacs 28, so the
> version of Org in GNU ELPA should have the fix.
> Steve Berman
I'm using Org 9.4.4 which came with Emacs 27.2. I'll upgrade.
Thank you all for the info.
parent reply other threads:[~2021-11-15 3:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <email@example.com>]
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).