Nicolas Goaziou writes:
> tftor...@tftorrey.com (T.F. Torrey) writes:
>
>> This almost works, I think ...
>>
>> #+name: snippet-awesome
>> #+begin_src org :exports results :results raw
>> Snippet of awesome text that changes sometimes. #+end_src
>>
>> #+HTML:
>> #+CALL: snippet-awesome :results
T.F. Torrey wrote:
> ...
> This almost works, I think ...
>
> #+name: snippet-awesome
> #+begin_src org :exports results :results raw
> Snippet of awesome text that changes sometimes.
> #+end_src
>
> #+HTML:
> #+CALL: snippet-awesome :results raw
> #+HTML:
>
> ... except that it doesn't act
tftor...@tftorrey.com (T.F. Torrey) writes:
> This almost works, I think ...
>
> #+name: snippet-awesome
> #+begin_src org :exports results :results raw
> Snippet of awesome text that changes sometimes. #+end_src
>
> #+HTML:
> #+CALL: snippet-awesome :results raw
> #+HTML:
>
> ... except that it
Hello Nicolas,
Nicolas Goaziou writes:
> tftor...@tftorrey.com (T.F. Torrey) writes:
>
>> Perhaps. We still know of no easy/straightforward way at all to
>> replicate using babel the behavior I had (creating '> class="foo">bar' with a macro), let alone in a pair of single
>> lines.
>
> Here is
tftor...@tftorrey.com (T.F. Torrey) writes:
> Perhaps. We still know of no easy/straightforward way at all to
> replicate using babel the behavior I had (creating ' class="foo">bar' with a macro), let alone in a pair of single
> lines.
Here is an example. Babel specialists can help you further.
Hello Nicolas,
Thank your for your thoughtful reply.
Nicolas Goaziou writes:
> tftor...@tftorrey.com (T.F. Torrey) writes:
>
>> 1. You wrote before that macros were scaled back because what they did
>> could be done by babel. Is that really a good reason for removing
>> functionality? Everyth
tftor...@tftorrey.com (T.F. Torrey) writes:
> 1. You wrote before that macros were scaled back because what they did
> could be done by babel. Is that really a good reason for removing
> functionality? Everything that Org does could be done in other tools,
> and yet ... we have Org.
Macros were
Hello Nicolas,
Thank you for your thoughtful clarification about macros in the new
exporter. Probably in the long run I will find happiness using babel
for what I want to do. In the meantime, however, I have a few more
questions:
1. You wrote before that macros were scaled back because what the
Hello,
tftor...@tftorrey.com (T.F. Torrey) writes:
> Nicolas Goaziou writes:
>
>> On that topic, the main difference with the previous exporter is that
>> macros are now required to be in a context that can be parsed. Thus, for
>> example, the following is not a macro:
>>
>> ~{{{title}}}~
>
>
Hello again,
Like many others, I'm adapting my workflow to the new exporter. Like
Carsten (but apparently few others), I've been using macros extensively.
Though I've spent several days digging through the mailing list and
code, I still don't have the answers I need, but hopefully I can ask
intel
Hello,
tftor...@tftorrey.com (T.F. Torrey) writes:
> Right now, though, it's giving me a small problem: in the export to
> HTML, macro's are not expanded, so I have {{{title}}}, for instance, in
> the HTML output.
>
> I haven't been following the list as closely as I'd like, so I'm hoping
> I mis
Hello all,
I really like the new exporter, and I appreciate the hard work of
everyone involved.
Right now, though, it's giving me a small problem: in the export to
HTML, macro's are not expanded, so I have {{{title}}}, for instance, in
the HTML output.
I haven't been following the list as closel
12 matches
Mail list logo
