From mboxrd@z Thu Jan 1 00:00:00 1970 From: Achim Gratz Subject: Re: Build fail with emacs 24.3.1 Date: Thu, 14 Mar 2013 08:26:17 +0000 (UTC) Message-ID: References: <4213D585-9331-41E2-AA2B-03550D3E043B@univie.ac.at> <878v5reck1.fsf@bzg.ath.cx> <8738vznjw9.fsf@Rainer.invalid> <87wqtalnlc.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:51255) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UG3Uh-0002qZ-DP for emacs-orgmode@gnu.org; Thu, 14 Mar 2013 04:26:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UG3Ug-00061o-CP for emacs-orgmode@gnu.org; Thu, 14 Mar 2013 04:26:35 -0400 Received: from plane.gmane.org ([80.91.229.3]:49575) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UG3Ug-00061h-5U for emacs-orgmode@gnu.org; Thu, 14 Mar 2013 04:26:34 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UG3V0-0006Bh-LY for emacs-orgmode@gnu.org; Thu, 14 Mar 2013 09:26:54 +0100 Received: from 217.10.52.10 ([217.10.52.10]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 14 Mar 2013 09:26:54 +0100 Received: from Stromeko by 217.10.52.10 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 14 Mar 2013 09:26:54 +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: emacs-orgmode@gnu.org Bastien altern.org> writes: > One potential problem in the first test is the use of "parent" as the > name of the symbol to pass to the macro... since this is the very same > name than the macro second argument. At least this reminded me this > section of Elisp manual: I've actually tested this by renaming the macro arguments and no symbol capturing seems to be involved via this path. The symbol is never used unquoted in the macro expansion anyway. > So... instead of fixing the macro calls in the tests, I've been > wondering why using a macro for `org-export-define-derived-backend' > and `org-export-define-backend' would be better? I think that these are proper uses of macros since Nicolas is introducing special syntax for defining a backend. In any case before anything is changed we should know why this is happening at all. Regards, Achim.