From mboxrd@z Thu Jan 1 00:00:00 1970 From: tsd@tsdye.com (Thomas S. Dye) Subject: Re: Unexpected macro error Date: Fri, 21 Nov 2014 19:13:10 -1000 Message-ID: References: <871tow5fk9.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46244) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xs30j-0003XT-VT for emacs-orgmode@gnu.org; Sat, 22 Nov 2014 00:13:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xs30d-0005eB-Iy for emacs-orgmode@gnu.org; Sat, 22 Nov 2014 00:13:29 -0500 Received: from gproxy8-pub.mail.unifiedlayer.com ([67.222.33.93]:38177) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1Xs30d-0005dz-CC for emacs-orgmode@gnu.org; Sat, 22 Nov 2014 00:13:23 -0500 Received: from [98.155.255.145] (port=62441 helo=manifi) by box472.bluehost.com with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.82) (envelope-from ) id 1Xs30U-0002fS-7V for emacs-orgmode@gnu.org; Fri, 21 Nov 2014 22:13:14 -0700 In-Reply-To: <871tow5fk9.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Fri, 21 Nov 2014 23:55:50 +0100") 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: Org-mode Aloha Nicolas, Nicolas Goaziou writes: > Hello, > > tsd@tsdye.com (Thomas S. Dye) writes: > >> A document I've been working on for several weeks broke recently without >> changes on my part. However, I've been tracking the master git branch >> every once in a while and I suspect some change in Org is the culprit. >> >> Org-mode version 8.3beta (release_8.3beta-580-g787733 @ >> /Users/dk/.emacs.d/src/org-mode/lisp/) >> >> I haven't tried to make an ECM because I don't know what the problem >> could be. Here is a backtrace: >> >> Debugger entered--Lisp error: (error "Undefined Org macro: ad; aborting.") > > [...] > >> The error message refers to a macro, ad. I don't have an "ad" macro. >> Where does this come from? > > There is probably a left over {{{ad}}} somewhere, which cannot be > expanded. An {{{ad}}} in a :noexport: section for several months began acting up recently. Now that it's gone, things work again. Thanks for pointing me in the right direction. All the best, Tom -- Thomas S. Dye http://www.tsdye.com