From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaron Ecay Subject: Re: org-collector unable to handle macros Date: Mon, 28 Sep 2015 22:03:45 +0100 Message-ID: <87r3li45ou.fsf@gmail.com> References: <55E0FCB4.2000305@verizon.net> <87mvx73wnz.fsf@nicolasgoaziou.fr> <87egij3w4b.fsf@nicolasgoaziou.fr> <87d1xshgtf.fsf@nicolasgoaziou.fr> <87bndbd1t1.fsf@gmail.com> <87h9mqtznz.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42460) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zgfac-0006bl-Mq for emacs-orgmode@gnu.org; Mon, 28 Sep 2015 17:04:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZgfaY-0004br-NM for emacs-orgmode@gnu.org; Mon, 28 Sep 2015 17:04:02 -0400 Received: from mail-wi0-x233.google.com ([2a00:1450:400c:c05::233]:35653) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZgfaY-0004bX-Hz for emacs-orgmode@gnu.org; Mon, 28 Sep 2015 17:03:58 -0400 Received: by wicge5 with SMTP id ge5so122886753wic.0 for ; Mon, 28 Sep 2015 14:03:58 -0700 (PDT) In-Reply-To: <87h9mqtznz.fsf@nicolasgoaziou.fr> 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: Nicolas Goaziou , Mark Edgington Cc: emacs-orgmode@gnu.org Hi Nicolas, 2015ko irailak 19an, Nicolas Goaziou-ek idatzi zuen: >=20 > Hello, >=20 > Aaron Ecay writes: >=20 >> This looks like the same problem I reported (and provided a patch for) h= ere: >> . Some orgtbl-* >> functions can=E2=80=99t cope with macro (or macro-resembling) text, beca= use they >> use the exporter, which expects all macros to have valid definitions. >>=20 >> Hopefully this time the bug can actually get fixed, instead of becoming >> bogged down in irrelevant aspects of the context in which it is >> reported. >=20 > Fixed. Thank you. Thanks. I can confirm that the bug no longer manifests in the context I reported (babel results). --=20 Aaron Ecay