From: Kyle Meyer <email@example.com>
To: "Ryan C. Thompson" <firstname.lastname@example.org>, email@example.com
Subject: Re: Bug: org-eldoc should require org-refile [9.3.6 (release_9.3.6-442-g97f0f1 @ /home/ryan/.emacs.d/straight/build/org-plus-contrib/)]
Date: Thu, 16 Apr 2020 02:52:01 +0000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
"Ryan C. Thompson" <email@example.com> writes:
> `org-eldoc-get-breadcrumb' in org-eldoc.el calls `org-get-outline-path'
> which is defined in org-refile.el, but org-eldoc does not load
> org-refile. This results in void-function errors when the Eldoc idle
> timer runs in an org buffer, unless you manually load org-refile. To fix
> this, org-eldoc should load org-refile.
Thanks for the report. This is related to the recent move of some
org.el code to org-refile.el. While your suggestion would resolve the
issue, there are other dependency issues with that org-refile.el change.
I proposed a large fix [^1] in a related thread:
That will resolve this issue as well, so let's see what comes of that.
prev parent reply other threads:[~2020-04-16 2:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 21:19 Bug: org-eldoc should require org-refile [9.3.6 (release_9.3.6-442-g97f0f1 @ /home/ryan/.emacs.d/straight/build/org-plus-contrib/)] Ryan C. Thompson
2020-04-16 2:52 ` Kyle Meyer [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).