Sebastian Rose writes:
> Ulf Stegemann writes:
>> When writing documentations I often come across expressions like
>>
>> doMagic('myVariable')
>>
>> In an ideal world the HTML code for this after exporting the org file
>> would look like this:
>>
>> doMagic('myVariable')
>
>
> Example:
>
>
>
Haha, just for the fun of it: While trying to document this via
Org-mode, I had to define this macro here:
#+MACRO: macro {{{$1}}}
* Predefined Macros
* ={{{macro(date(TIME_FORMAT_STRING))}}}=
* ={{{macro(modification-time(TIME_FORMAT_STRING))}}}=
* ={{{macro(time(TIME_F
Ulf Stegemann writes:
> When writing documentations I often come across expressions like
>
> doMagic('myVariable')
>
> In an ideal world the HTML code for this after exporting the org file
> would look like this:
>
> doMagic('myVariable')
Example:
#+MACRO: macname (eval (format "Macro sa
--- Gio 9/7/09, Ulf Stegemann ha scritto:
> When writing documentations I often
> come across expressions like
>
> doMagic('myVariable')
>
> In an ideal world the HTML code for this after exporting
> the org file
> would look like this:
>
>
> doMagic('myVariable')
>
> The purpose is of co
When writing documentations I often come across expressions like
doMagic('myVariable')
In an ideal world the HTML code for this after exporting the org file
would look like this:
doMagic('myVariable')
The purpose is of course to indicate that `doMagic' is a literal
function/method name whil
