Search results
Jump to navigation
Jump to search
Create the page "Command/value:lua" on this wiki! See also the search results found.
Page title matches
- <h1 class="command">\Lua</h1> <div class="cd:shortdesc"><!-- a short command summary goes here -->718 bytes (108 words) - 18:58, 19 September 2020
Page text matches
- <h1 class="command">\Lua</h1> <div class="cd:shortdesc"><!-- a short command summary goes here -->718 bytes (108 words) - 18:58, 19 September 2020
- <h1 class="command">\startctxfunctiondefinition ... \stopctxfunctiondefinition</h1> <div class="cd:shortdesc"><!-- a short command summary goes here -->1 KB (167 words) - 16:42, 27 August 2020
- <td>''valid argument(s) for Lua's `context()` function''</td> Pass an argument to Lua's {{code|context(...)}} command. The text is1 KB (138 words) - 17:26, 12 November 2019
- <h1 class="command">\startctxfunction ... \stopctxfunction</h1> <!-- a short command summary goes here -->1 KB (173 words) - 14:57, 27 August 2020
- <td>''lua code''</td> ...it. Advantage: you can pass the contents of macro parameters like `#1` to Lua. Disadvantage: everything after a percent sign is ignored, and once the com1 KB (150 words) - 19:43, 8 June 2020
- <td>''a valid way to end `context.` in Lua''</td> Execute a ConTeXt command via lookup in the {{code|context}} table in LuaTeX. Defined as follows:1 KB (146 words) - 17:26, 12 November 2019
- Run/compile a ConTexT Lua document. Defined as follows: * [[CLD|ConTeXt Lua document]]983 bytes (106 words) - 17:26, 12 November 2019
- ...Document) is the environment which lets you interact with TeX from inside Lua code. For more informations on this see the manual cld-mkiv.pdf, which is i Now if one needs to pass arguments from Lua to a macro command defined in ConTeXt, one has several possibilities.3 KB (482 words) - 15:31, 14 December 2020
- %\setvariable{NAME}{KEY}{VALUE} => \getvariable{NAME}{KEY} === Example 2: Using Lua ===2 KB (227 words) - 23:52, 8 September 2023
- <h1 class="command">\ctxfunction</h1> <div class="cd:shortdesc"><!-- a short command summary goes here -->1 KB (139 words) - 16:42, 27 August 2020
- <h1 class="command">\ctxluabuffer</h1> <div class="cd:shortdesc"><!-- a short command summary goes here -->817 bytes (115 words) - 10:07, 16 November 2022
- <td>''lua command from in the'' command ''table''</td> To quickly access Lua commands in the {{code|command}} table.1 KB (162 words) - 17:26, 12 November 2019
- <td>[[Command/value:IDENTIFIER|IDENTIFIER]] </td> <td class="cmd">[[Command/keyword:option|option]]</td>3 KB (461 words) - 16:02, 21 March 2023
- <h1 class="command">\setregisterentry</h1> <div class="cd:shortdesc"><!-- a short command summary goes here -->3 KB (314 words) - 10:05, 13 October 2020
- <h1 class="command">\<i>ctxfunction</i></h1> <!-- a short command summary goes here -->940 bytes (125 words) - 15:00, 27 August 2020
- <h1 class="command">\<i>ctxfunctiondefinition</i></h1> <!-- a short command summary goes here -->798 bytes (107 words) - 14:49, 27 August 2020
- ...language at your fingertips. All <code>\xml...</code> commands have their Lua counterparts. Unfortunately, this is not yet fully documented, so this wiki ...e> commands allow you to work with the content of your xml elements within Lua; <code>lxml...</code> commands pass the content to ConTeXt and typeset it.7 KB (1,105 words) - 08:27, 2 July 2022
- <td class="cmd">[[Command/keyword:r|r]]</td> <td>[[Command/value:number|number]] red channel (RGB)</td>5 KB (722 words) - 13:46, 8 June 2020
- ...used. But one can also think of the components that make up ConTeXt code: Lua, MetaPost, TeX, and XML. But once it is clear to a user what (s)he is deali * There is no PDF backend code, all PDF generation is handled by ConTeXt’s Lua code.4 KB (606 words) - 09:43, 1 July 2022
- ..."second"> ... </span><span class="third"> ... </span><span class="fourth" >command</span><span class="fifth" > ... </span></td> beginning of the document. The command features several modifier sequences,4 KB (447 words) - 09:24, 7 August 2020