emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Julien Chastang <chastang@ucar.edu>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-publish-project yields "Eager macro-expansion failure"
Date: Wed, 17 Jun 2015 17:44:55 -0600	[thread overview]
Message-ID: <CALc0GAax=gKmFaDQOs8D7W0czYe0WVqZFc5Uj22vwS9BE1Wc7w@mail.gmail.com> (raw)
In-Reply-To: <87616mmoou.fsf@pierrot.dokosmarshall.org>

Nick,

Thanks for the feedback. I ultimately fixed this problem by moving my
org-mode customizations in my emacs initialization file after the
package initialization of orgmode.org/elpa. I somehow think this
problem is related to having two versions of org floating around, one
from emacs itself and the other from orgmode.org/elpa. (My emacs
initialization file is done via tangle/org-babel so I have to have org
available from the start, I presume.) BTW, this problem would occur in
several situations. For example, when I was trying to get an agenda
view. At any rate, the issue is resolved for now.

Thanks again for your suggestions.


On Wed, Jun 17, 2015 at 7:47 AM, Nick Dokos <ndokos@gmail.com> wrote:
> 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
>
>



-- 
Julien Chastang
Scientific Software Developer
Unidata-UCAR

     prev parent reply	other threads:[~2015-06-17 23:45 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
2015-06-17 23:44   ` Julien Chastang [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:
  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='CALc0GAax=gKmFaDQOs8D7W0czYe0WVqZFc5Uj22vwS9BE1Wc7w@mail.gmail.com' \
    --to=chastang@ucar.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@gmail.com \
    /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

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