I have a lot of variables defining paths of specifications so each specification can refer to others, and all the concrete URLs can be changed easily in one place if need be.

Here's an example:

This specification is in the {spec_status} state. The development version of this document can be found at {openehr_rm_common}[{openehr_rm_common}^].

The variable openehr_rm_common contains a reference to another variable {rm_release}, which can be set to things like 'latest', 'Release-1.0.2' and so on.

In the particular para quoted above, I always want the variable rm_release to be 'latest', even when I set rm_release to Release-1.2.5 from the command line. So it's a reversal of what seems to be possible in the current system.

It seems an obvious thing to want, and I thought that maybe something like this would work:

[rm_release="latest"]
This specification is in the {spec_status} state. The development version of this document can be found at {openehr_rm_common}[{openehr_rm_common}^].

But it doesn't. So far I can't find any way to solve this problem other than to define a whole parallel set of variables like openehr_rm_common_latest, of which there will be about 30. Which seems painful.

Anyone have any ideas?

---

If you reply to this email, your message will be added to the discussion below:

http://discuss.asciidoctor.org/How-to-override-a-variable-for-a-block-tp6693.html

To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML