<- [[code|Why Use Code]] --------- [[expression|About Expressions]]-> ===== <> ===== The <> macro lets you display the full contents of a passage inside another passage. ====Usage==== Long form: >%%<<%%display //expression//%%>>%% Shorthand form (see below): >%%<<%%//[[expression|string]]// //[value ...]//%%>>%% ====Motivating example==== Suppose you have a block of text or code which appears identically in multiple passages. It can be a pain to have to keep track of each instance in which it was used, especially when fixing spelling or link names. <> provides you with an elegant means of reusing this text: simply place it in another passage, and then use <> in each of the places it is used. Consider this example: {{ :display2.png |}} In all 3 of the above passages, the entire text of the passage "window" will be displayed after the text, thus saving the need to reproduce it exactly in each passage. ====A note about tags==== What the <> macro actually does is copy the text from the given passage into the current passage. It doesn't actually display the passage in its own right. What this means is that, if a passage has [[tag]]-based CSS styling specific to it, then that styling will not be applied to the current passage! ====Using a variable to display a passage==== The <> macro treats its argument as a [[about expressions|code expression]]. This means that you can put a passage name in a variable and then display it: With a rush of wind, you arrive in the <>! <> If, say, $destination contained the string "Cellar", and a Cellar passage existed, it would print "With a rush of wind, you arrive in the Cellar!" and display the Cellar passage. ====Shorthand form==== The <> macro is special among Twine macros because it has a shorthand form. Instead of writing <>, you can simply write <>, as if it was another macro. However, to avoid conflicts with other aspects of Twine syntax, you can only use the shorthand to display passages whose names adhere to these rules: * The passage name must not contain spaces. * The passage name must not conflict with the name of an actual macro (so, you can't display a passage titled "print"). This shorthand form allows you to write Twine stories in a "template" style: {{ :display.png |}} As you can see, the "battlecry" and "minions" passages can be displayed in place of those <<[[if]]>> statements throughout the story, with little hindrance to the readability of the passage text. (The two passages use the [[tag|nobr tag]] to eliminate line-breaks.) ====Passing data to displayed passages==== See the documentation for the [[function#parameter_number|parameter()]] function. ====Displaying a script passage==== If you attempt to <> a passage containing a Javascript [[script]], something special will happen: the script code will not be displayed, but will instead be re-executed. ====Avoid the <> loop==== It is possible to lock up a reader's Web browser by using the ''<>'' macro improperly, like this: :: Oops <> When displayed, the passage will keep attempting to display itself over and over until the reader force quits his Web browser. This doesn't do permanent damage, but it will not endear yourself to your reader. <- [[code|Why Use Code]] --------- [[expression|About Expressions]]->