Re: [O] parameterizing keyword values during a #+call

2013-05-01 Thread Greg Minshall
Gary, Org-mode macros that got expanded in the middle of babel source block text would be cool. Just saying. i agree with Eric's comment. if you think of the issue of trying to parse an arbitrary (and growing) number of languages, trying to avoid language-specific constructions in your choice

Re: [O] parameterizing keyword values during a #+call

2013-04-30 Thread Greg Minshall
Eric, just for completeness, and in case this may be of use to other people, below is the result of my question + your suggestions. the following illustrates org-mode plus asymptote producing a .svg file during html export, and a pdf file during any other (presumably, latex) export. thanks

Re: [O] parameterizing keyword values during a #+call

2013-04-30 Thread Gary Oberbrunner
I've been having the same issue (exporting to HTML and PDF, and need all my graphics filenames to adjust automatically). I mostly don't use #+CALL though; I just have src blocks. #+BEGIN_SRC python :session UDpython :exports results :results file do_hbar('/tmp/machines-by-os.pdf', (8,1.5),

Re: [O] parameterizing keyword values during a #+call

2013-04-30 Thread Eric Schulte
Gary Oberbrunner ga...@oberbrunner.com writes: I've been having the same issue (exporting to HTML and PDF, and need all my graphics filenames to adjust automatically). I mostly don't use #+CALL though; I just have src blocks. #+BEGIN_SRC python :session UDpython :exports results :results

Re: [O] parameterizing keyword values during a #+call

2013-04-26 Thread Greg Minshall
Eric, thanks! Something like the following should work. #+call: disc[:file (if (and (boundp org-export-current-backend) (equal org-export-current-backend 'html)) foo.svg foo.tex)]() :results file in fact, with the new exporter, org-export-current-backend has bit the dust, but apparently

Re: [O] parameterizing keyword values during a #+call

2013-04-26 Thread Greg Minshall
Eric, And you could wrap up the extra-long Emacs-lisp in a function or macro in your init to avoid the overlength header argument. is it possible to embed the function inside the .org file itself? (in order to promote sharing of .org files, without needing any more-than-necessary ancillary

Re: [O] parameterizing keyword values during a #+call

2013-04-26 Thread Eric Schulte
Greg Minshall minsh...@umich.edu writes: Eric, And you could wrap up the extra-long Emacs-lisp in a function or macro in your init to avoid the overlength header argument. is it possible to embed the function inside the .org file itself? (in order to promote sharing of .org files, without

Re: [O] parameterizing keyword values during a #+call

2013-04-26 Thread Greg Minshall
Eric, You could put the emacs-lisp code into an emacs-lisp code block which is exported but has a result type of none or silent. ah -- i should have tried that! that works -- thanks *very* much! cheers, Greg

[O] parameterizing keyword values during a #+call

2013-04-25 Thread Greg Minshall
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

Re: [O] parameterizing keyword values during a #+call

2013-04-25 Thread Eric Schulte
Greg Minshall minsh...@umich.edu writes: 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