An Odd Macro Call

1

This is a confusing macro call! but it works!

<$set name=mac  value=100>

<$macrocall $name=mac $output="text/plain" />

</$set>
2

Every time I bump into that I say to myself, “Shit, I must remember that $output…”

But I won’t. :confused:

3

It proves what the doco says

  • macros are paramatised text replacements
  • \define varname is equivalent to set

But what does it all mean?

4

:scream:

OMG, now you’ve done it. It might be almost bedtime for you, Tones, but my day is just getting started. I can hear all the philosophers crawling out from the woodwork now. Look! Here comes @TiddlyTitch armed with ten YT links and a bevvy of obscure quotations. :upside_down_face:

Sorry, couldn’t resist

5

Or

<$set name=mac  value="<h1>Hi there!</h1>">

<$macrocall $name=mac $output="text/html" />

</$set>

Aardvark comes before zebra, except in a foot race.

6

Actualy,

I was thinking what if we could use $output and/or $type in the shortcut macro?

<<mymacro $output="text/plain">> etc…
and [<mymacro $output="text/plain">]

It may allow us to find an alternative to needing to wrap macro with wikify to force a macro to evaluate.