3,897
edits
Changes
Jump to navigation
Jump to search
System Macros/User Interaction (view source)
Revision as of 09:30, 1 August 2006
, 09:30, 1 August 2006split off section
[[System_Macros]]
This macro hardly needs explanation. It stops TeX until you input something.
Macros for showing messages. In the multi-lingual modules, we will also introduce a mechanism for message passing. For the moment we stick to the core macros:
<texcode>
\writestring {string}
\writeline
\writestatus {category} {message}
</texcode>
Messages are formatted: the category appears within a fixed number of columns, on it's own, followed by a colon. One can provide the maximum width of the identification string with the macro <code>\statuswidth</code>.
For debugging purposes we can enhance macros with the next alternative. Here <code>debuggerinfo</code> stands for both a macro accepting two arguments and a boolean (in fact a few macro's too).
<texcode>
\debuggerinfo {subcategory} {message}
</texcode>
This message will only be output if <code>\debuggerinfo</code> is true. (it usually isn't). If you need to calculate something to be used inside the message, embrace your calculating code with <code>\ifdebuggerinfo ... \fi</code>.
This macro hardly needs explanation. It stops TeX until you input something.
Macros for showing messages. In the multi-lingual modules, we will also introduce a mechanism for message passing. For the moment we stick to the core macros:
<texcode>
\writestring {string}
\writeline
\writestatus {category} {message}
</texcode>
Messages are formatted: the category appears within a fixed number of columns, on it's own, followed by a colon. One can provide the maximum width of the identification string with the macro <code>\statuswidth</code>.
For debugging purposes we can enhance macros with the next alternative. Here <code>debuggerinfo</code> stands for both a macro accepting two arguments and a boolean (in fact a few macro's too).
<texcode>
\debuggerinfo {subcategory} {message}
</texcode>
This message will only be output if <code>\debuggerinfo</code> is true. (it usually isn't). If you need to calculate something to be used inside the message, embrace your calculating code with <code>\ifdebuggerinfo ... \fi</code>.
