emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-publish-project yields "Eager macro-expansion failure"
Date: Wed, 17 Jun 2015 09:47:45 -0400	[thread overview]
Message-ID: <87616mmoou.fsf@pierrot.dokosmarshall.org> (raw)
In-Reply-To: CALc0GAbtQ_+bVjdXUYevyJaXhYf7AbVFT_pgjXN78RWK9qTnyw@mail.gmail.com

Julien Chastang <chastang@ucar.edu> writes:

> Hello.
>
> Frequently, when I try to org-publish-project, I get a "Eager
> macro-expansion failure"
>
> The message buffer and backtrace are available here:
>
> https://gist.github.com/julienchastang/98b268e9601882d8d81c
>
> Indeed, I can simply reproduce this problem by calling
>
> (load-with-code-conversion "<path>/elpa/org-20150615/ox-html.el"
> "<path>/elpa/org-20150615/ox-html.el" nil t)
>
> which gets called somewhere  in the org-publish-project invocation
> (see backtrace). So I am concluding the error has nothing to do with
> my project.
>
> What can I do to publish my project again?
>
> Many thanks.

Can you try with uncompiled code? See

(info "(org) Feedback")

for how to do that.

There are two possibilities:

o you'll still get the error, but the backtrace will be much
  more informative.
o you will not get the error - IME, problems that disappear when
  run with uncompiled code are harder to debug. But that would still
  be interesting information.

In the latter case, a minimal example that triggers the error would
be useful.

-- 
Nick

  reply	other threads:[~2015-06-17 13:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 20:59 org-publish-project yields "Eager macro-expansion failure" Julien Chastang
2015-06-17 13:47 ` Nick Dokos [this message]
2015-06-17 23:44   ` Julien Chastang

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

  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=87616mmoou.fsf@pierrot.dokosmarshall.org \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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