emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: John Goerzen <jgoerzen@complete.org>, emacs-orgmode@gnu.org
Subject: Re: Bug: 20200525 release: invalid function: org-preserve-local-variables [9.3.6 (9.3.6-75-gb614ed-elpa @ /home/jgoerzen/.emacs.d/elpa/org-20200525/)]
Date: Thu, 28 May 2020 01:53:40 +0000	[thread overview]
Message-ID: <87lflcx1sr.fsf@kyleam.com> (raw)
In-Reply-To: <87blm9a32x.fsf@complete.org>

John Goerzen writes:

> I recently have upgraded to org 20200525 from your package repo because
> org-roam requires a newer org-mode than I had.  GNU ELPA has 9.3.6,
> which would be new enough, but all of my machines fail downloading the
> tar of that version from ELPA with "invalid request", so I'm on
> 20200525.
> Many actions, and in particular refile, produce:
> Invalid function: org-preserve-local-variables
> and fail.
> (org-refile) is defined in org.el but why it doesn't seem to be seeing
> org-macs is beyond me.

I installed elpa/org-20200525 in a vanilla environment, and I wasn't
able to trigger any similar failures when refiling.  My best guess is
that it's due to an interaction with the older Org that comes built-in
with Emacs and lacks the org-preserve-local-variables macro.  It's
probably worth uninstalling/reinstalling, making sure the built-in Org
isn't loaded.

      reply	other threads:[~2020-05-28  1:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27 14:02 Bug: 20200525 release: invalid function: org-preserve-local-variables [9.3.6 (9.3.6-75-gb614ed-elpa @ /home/jgoerzen/.emacs.d/elpa/org-20200525/)] John Goerzen
2020-05-28  1:53 ` Kyle Meyer [this message]

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lflcx1sr.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jgoerzen@complete.org \


* 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).