From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [PATCH] inline src block results can be removed Date: Thu, 13 Nov 2014 18:48:19 +0100 Message-ID: <8761ejq9ek.fsf@nicolasgoaziou.fr> References: <87egt81acy.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47377) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XoyUl-0000Lu-Hg for emacs-orgmode@gnu.org; Thu, 13 Nov 2014 12:47:55 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XoyUd-00048h-Pq for emacs-orgmode@gnu.org; Thu, 13 Nov 2014 12:47:47 -0500 Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:49803) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XoyUd-00045x-J3 for emacs-orgmode@gnu.org; Thu, 13 Nov 2014 12:47:39 -0500 In-Reply-To: (Charles C. Berry's message of "Wed, 12 Nov 2014 15:47:07 -0800") 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: "Charles C. Berry" Cc: Aaron Ecay , Andreas Leha , emacs-orgmode@gnu.org, Ista Zahn , mcg Hello, "Charles C. Berry" writes: > I like the flexibility that macros would allow. I like it too. Macros are much better than export snippets for the task. > I don't think the usual #+MACRO works here, as the definition would be > found in `org-macro-templates' by the first call and existing stuff > would be expanded instead of being left for babel to remove it. But > setting it up as a document keyword should work, right? > > Don't know if there are other gotchas. > > Maybe a limited collection of formats could be set up to support basic > markup options and the macro could choose amongst them with a second > arg set by a babel header arg. I think {{{results()}}} should remain a dumb wrapper itself and not try to do some formatting (i.e., a simple, hard-coded macro). Formatting should be on the side of Babel and, possibly, its arguments. Let's not duplicate features. > I am not quite sure how to marry this to header args. Maybe the :wrap > header arg should be hijacked for inline src blocks to specify a macro > for the results. Macro can be the default output. If you don't want a macro, use raw header. IOW, there is no need for a specific header arg. > I mean, does anyone actually use stuff like src_R[:wrap latex]{1+2}? > The current result cannot be parsed as an export block, AFAICS. It could evaluate to @@latex:3@@. Parsing can also be solved if necessary. Thanks for your work. Regards, -- Nicolas Goaziou