Attribute = expression

Most export mark-up expressions are now permitted in Agent and Container actions. (Some actions only make sense in the context of HTML export; for example, those that refer to files — these elements are ignored)

For example:

Name=^ made on 04-Sep-16

... sets the name of a note to a formatted date.

Note the the template expression begins with a caret (^) followed by a space. The space character is ignored (but subsequent spaces are treated as space characters. This avoids possible ambiguities where Tinderbox might not know whether you intended the initial word to be a mark-up token. For example, in

Name=^ides of march

... Tinderbox would try to evaluate ^ides as a mark-up expression, whereas this,

Name=^ ^ides of march

... would set the Name attribute to the string "ides of March"

The space is optional and may be omitted in the (common) case where the template expression begins with a command

Name=^get(Date)^ jottings

Multiple actions may be separated with semicolons, even if some of them are template expressions. Previously, if you were using a template expression, semicolons were prohibited.

Note that semicolons may not appear inside a template expression action, since the parser would split the expression at the semicolon. Thus

Name=^get(user1)^;Color=red;

... works as expected but ...

Name=^ Sing; Dance

... does not give what you'd expect. In the second example, the name of the note is set to Sing, and the stamp named 'Dance' is then applied to the note.

Licensed under Creative Commons Attribution-Noncommercial-Share Alike 3.0 License
[See aTbRef CC licence Attribution/Waiver info info]