From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg Minshall Subject: parameterizing keyword values during a #+call Date: Thu, 25 Apr 2013 19:45:53 -0400 Message-ID: <94981.1366933553@greg-minshalls-mbp.local> Return-path: Received: from eggs.gnu.org ([208.118.235.92]:46042) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UVVrP-0003sa-QT for emacs-orgmode@gnu.org; Thu, 25 Apr 2013 19:45:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UVVrN-0005aM-Cx for emacs-orgmode@gnu.org; Thu, 25 Apr 2013 19:45:55 -0400 Received: from relay03.pair.com ([209.68.5.17]:4453) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1UVVrN-0005aH-4s for emacs-orgmode@gnu.org; Thu, 25 Apr 2013 19:45:53 -0400 Received: from greg-minshalls-mbp.local (localhost [127.0.0.1]) by gregair.cliq.com (Postfix) with ESMTP id 13D8A10B5286A for ; Thu, 25 Apr 2013 19:45:53 -0400 (EDT) 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 hi. i would have an org file that uses lots of #+calls to various asymptote routines (babelled into the file) to produce graphics. i would like to export this file to both html and to latex (specifically beamer). for html, i would like, e.g., SVG files, and for latex, PDF files. the file name is normally passed to the asymptote routine via a :file parameter, to wit ---- #+call: disc[:file images/disc.svg]() :results file ---- and the file extension (".svg" in the above) determines the format of the asymptote output. is there an obvious way to allow the file extension to take on different values depending on which sort of export is driving its execution? i had hoped that replacing ".svg" with something like ".{{{ext()}}}", where "ext" was a macro which selected amongst the alternatives(*), would do the trick. but that doesn't appear to be the case. thanks in advance (and with full appreciation of what a pain macros are to implement fully, halfly, anyly), Greg Minshall (*) #+MACRO: ext @@latex:pdf@@@@beamer:pdf@@@@html:svg@@