From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: 30961@debbugs.gnu.org
Subject: bug#30961: Byte compilation problem with emacs-org
Date: Tue, 27 Mar 2018 16:20:24 +0200 [thread overview]
Message-ID: <m1y3idwqfr.fsf@fastmail.net> (raw)
An Emacs installation that includes package emacs-org exhibits a
well-documented bug: certain uses of org-babel, such as using the
R language, lead to the error message
Invalid function: org-babel-header-args-safe-fn
For a discussion of this bug in other contexts, see for example:
https://lists.gnu.org/archive/html/emacs-orgmode/2016-02/msg00415.html
I do not claim to fully understand the cause of this bug, but the
explanations mention a conflict between the org-mode version shipped
with Emacs and the later one being installed afterwards. This conflict
happens when the newer org-mode is byte-compiled, and leads to wrong
.elc files.
It is easy to verify that the Guix version also suffers from this
byte-compilation problem. Removing the "build" step, and thus byte
compilaion, by adding
(arguments
`(#:phases
(modify-phases %standard-phases
(delete 'build))))
to the definition of emacs-org removes the error message.
What I do not understand yet is why this happens within Guix. The
explanations for the bug concentrate on the built-in org-mode version
having been initialized before byte compilation of the new one, and
recommend starting Emacs with the –quick option for the byte compilation
session. This is what Guix does as well, so the problem should not
exist.
I tried to remove the old org-mode from load-path during byte
compilation of the new version by manipulating EMACSLOADPATH, so far
without success. If Emacs' basic "lisp" dir is not on EMACSLOADPATH,
Emacs fails to do anything, but if it is, Emacs automatically adds
"lisp/org" via lisp/subdir.el.
Konrad.
next reply other threads:[~2018-03-27 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 14:20 Konrad Hinsen [this message]
2018-03-27 14:43 ` bug#30961: Byte compilation problem with emacs-org Adonay Felipe Nogueira
2018-03-31 8:23 ` Konrad Hinsen
2019-12-08 21:38 ` Maxim Cournoyer
2019-12-09 8:52 ` Konrad Hinsen
2019-12-13 2:06 ` T460s laptop
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1y3idwqfr.fsf@fastmail.net \
--to=konrad.hinsen@fastmail.net \
--cc=30961@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.