| Since this is easy to implement now as an extension, I would oppose adding something like this as new syntax to the language, without a strong argument explaining why it’s a good idea.
The one feature I would like is to be able to define a bunch of these custom templates once for a set of documents, such as for an Antora or jekyll-asciidoc site. I don’t think this requires or would be influenced by a syntax change however.
David Jencks
I hesitate to say it, because it makes things even more complex, but substitution could be controlled by a switch in the defined block. Then the author would have control of when (and even whether) to substitute.
J
Yes, that sort of thing, but perhaps with a defined syntax, eg
define::some_name[parameter_list] . some contents . enddefine::[]
some_name::[parameters]
and not necessarily just a single block.
Also questions like use of document attributes (but not ones that are parameters) in the body, are they substituted in the define or after substitution (as yours are) or not allowed (my preference to avoid users complaining about the choice of define or substitution and issues about attributes with the same name being innocently used in the document with no intention of the define using it).
Cheers Lex
|
