From: Ihor Radchenko <email@example.com>
Subject: Bug: org-with-wide-buffer is used in org-refile.el without (require 'org-macs) [9.3.6 (release_9.3.6-441-gba6855 @ /home/yantar92/.emacs.d/straight/build/org/)]
Date: Tue, 07 Apr 2020 18:52:42 +0800 [thread overview]
Message-ID: <878sj74lfp.fsf@localhost> (raw)
Recently, I ran into a problem compiling org-mode asynchronously with
each .el file being compiled in a separate process (via
When I tried to compile org-refile.el in a separate Emacs process
(without compiling all other .el files), there was no way for the
byte-compiler to know that org-with-wide-buffer is a macro.
As I understand, normally org-mode compiles synchronously with all the
.el files being byte-compiled in alphabetic order. Then,
(eval-and-compile (require 'org-macs)) from org.el is defined prior
compiling all the org-*.el files, which accidentally allow the org-mode
to be compiled without any issues.
Note that I first reported this to bug-gnu-emacs mail-list , but it
seems that absence of (require 'org-macs) is wrong on the org-mode side.
Let me know what you think.
Emacs : GNU Emacs 28.0.50 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.13, cairo version 1.16.0)
Package: Org mode version 9.3.6 (release_9.3.6-441-gba6855 @ /home/yantar92/.emacs.d/straight/build/org/)
Center for Advancing Materials Performance from the Nanoscale (CAMP-nano)
State Key Laboratory for Mechanical Behavior of Materials, Xi'an Jiaotong University, Xi'an, China
Email: firstname.lastname@example.org, email@example.com
next reply other threads:[~2020-04-07 10:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 10:52 Ihor Radchenko [this message]
2020-04-10 3:22 ` Bug: org-with-wide-buffer is used in org-refile.el without (require 'org-macs) [9.3.6 (release_9.3.6-441-gba6855 @ /home/yantar92/.emacs.d/straight/build/org/)] Kyle Meyer
2020-04-16 2:54 ` Kyle Meyer
2020-05-31 14:49 ` Ihor Radchenko
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).