Re: looking for a macro eval workaround (9.1 vs 9.2 and +) for export backend test

2020-11-29 Thread Tom Gillespie
Not sure if this helps, but the example that I came up with for the quickstart https://orgmode.org/quickstart.html#macros has an example (see below) of using multiple @@ export snippets in a single macro. If you have consistent naming conventions for pdf vs svg you might be able to write a variant

Re: looking for a macro eval workaround (9.1 vs 9.2 and +) for export backend test

2020-11-29 Thread Eric S Fraga
On Sunday, 29 Nov 2020 at 18:30, Bruno BEAUFILS wrote: > Any way this nice clean solution works well for almost all my cases > but one: when I include image I want them to be in pdf format in LaTeX > export and in original svg source when exporting in HTML. I used to do this the same way you are

Re: looking for a macro eval workaround (9.1 vs 9.2 and +) for export backend test

2020-11-29 Thread Bruno BEAUFILS
On Mon, Nov 23, 2020 at 01:12:45PM +, Eric S Fraga wrote: > Don't be too hard on yourself! :-) :-) Any way this nice clean solution works well for almost all my cases but one: when I include image I want them to be in pdf format in LaTeX export and in original svg source when exporting in

Re: looking for a macro eval workaround (9.1 vs 9.2 and +) for export backend test

2020-11-23 Thread Eric S Fraga
On Monday, 23 Nov 2020 at 14:02, Bruno BEAUFILS wrote: > I blame myself not having it in the first place. Don't be too hard on yourself! :-) Org, just like Emacs, has so many different ways of accomplishing anything that sometimes the easiest is overlooked! Glad I could help. -- : Eric S

Re: looking for a macro eval workaround (9.1 vs 9.2 and +) for export backend test

2020-11-23 Thread Bruno BEAUFILS
On Mon, Nov 23, 2020 at 10:19:16AM +, Eric S Fraga wrote: > Maybe define your macro like this: > > #+macro: hfill @@latex:\hfill@@ Very good idea indeed. I blame myself not having it in the first place. Thank's a lot! -- Bruno BEAUFILS signature.asc Description: PGP signature

Re: looking for a macro eval workaround (9.1 vs 9.2 and +) for export backend test

2020-11-23 Thread Eric S Fraga
Maybe define your macro like this: #+macro: hfill @@latex:\hfill@@ HTH, eric -- : Eric S Fraga via Emacs 28.0.50, Org release_9.4-118-g2a4578.dirty

Re: looking for a macro eval workaround (9.1 vs 9.2 and +) for export backend test

2020-11-22 Thread Bruno BEAUFILS
On Sun, Nov 22, 2020 at 12:18:07AM +1100, Tim Cross wrote: > Hmm, I just use backend specific blocks for this purpose. e.g. > > #+begin_export latex > \hfil{} > #+end_export Yes but it is what I try to avoid in order to let the file as simple and readable as possible. > IMO the org #+MACRO is

Re: looking for a macro eval workaround (9.1 vs 9.2 and +) for export backend test

2020-11-21 Thread Tim Cross
Bruno BEAUFILS writes: > I have a *lot* of org files with a macro =if-backend= which enables me > to decide what to export depending on the backend : > > #+begin_src org > #+macro: if-backend (eval (if (org-export-derived-backend-p > org-export-current-backend '$1) "$2")) > #+end_src > >