From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: org-publish-project yields "Eager macro-expansion failure" Date: Wed, 17 Jun 2015 09:47:45 -0400 Message-ID: <87616mmoou.fsf@pierrot.dokosmarshall.org> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51823) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z5Dhn-0005rP-8v for emacs-orgmode@gnu.org; Wed, 17 Jun 2015 09:48:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z5Dhj-00034Q-9C for emacs-orgmode@gnu.org; Wed, 17 Jun 2015 09:48:39 -0400 Received: from plane.gmane.org ([80.91.229.3]:47036) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z5Dhj-00034F-2a for emacs-orgmode@gnu.org; Wed, 17 Jun 2015 09:48:35 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Z5DhY-0004JF-Gv for emacs-orgmode@gnu.org; Wed, 17 Jun 2015 15:48:24 +0200 Received: from pool-108-20-41-47.bstnma.fios.verizon.net ([108.20.41.47]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 17 Jun 2015 15:48:24 +0200 Received: from ndokos by pool-108-20-41-47.bstnma.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 17 Jun 2015 15:48:24 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Julien Chastang 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 "/elpa/org-20150615/ox-html.el" > "/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