Search results
Create the page "ConTeXt Issues Lua" on this wiki! See also the search results found.
- <h1 class="command">\Lua</h1> The command <tt>\Lua</tt> typesets Lua.718 bytes (108 words) - 18:58, 19 September 2020
- ...ondefinition ... \stopctxfunctiondefinition</tt> defines a macro that is a lua function without arguments. ...s defines a TeX macro without arguments that when expanded runs a block of lua code instead of executing TeX commands.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
- <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
- The environment <tt>\startctxfunction ... \stopctxfunction</tt> defines a lua function from within TeX code. This defines a lua function without arguments that can be called from TeX using the {{cmd|ctxf1 KB (173 words) - 14:57, 27 August 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: \def\cldprocessfile#1{\directlua\zerocount{context.runfile("#1")}}983 bytes (106 words) - 17:26, 12 November 2019
- <context mode="mkiv" source="yes"> </context>2 KB (227 words) - 23:52, 8 September 2023
- <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
- * [[Category:Command/Lua]] <h2>Help from ConTeXt-Mailinglist/Forum</h2>817 bytes (115 words) - 10:07, 16 November 2022
- * [[Category:Command/Lua]] <h2>Help from ConTeXt-Mailinglist/Forum</h2>1 KB (139 words) - 16:42, 27 August 2020
- ...them inside <tt>["..."]</tt>, which is more robust form of putting key in Lua table, see example bellow. <h3>Processing on Lua end</h3>3 KB (314 words) - 10:05, 13 October 2020
- * [[Category:Command/Lua]] <h2>Help from ConTeXt-Mailinglist/Forum</h2>798 bytes (107 words) - 14:49, 27 August 2020
- * [[Category:Command/Lua]] <h2>Help from ConTeXt-Mailinglist/Forum</h2>940 bytes (125 words) - 15:00, 27 August 2020
- <context source="yes"> </context>1 KB (191 words) - 13:00, 8 May 2024
- ...nd/value:nested|nested]] [[Command/value:tex|tex]] [[Command/value:context|context]] [[Command/value:none|none]] [[Command/value:NAME|NAME]]</td> <context source="yes">3 KB (461 words) - 16:02, 21 March 2023
- <context source="yes"> </context>3 KB (409 words) - 17:27, 8 May 2024
- ...unless they are direct clones. In that case, the new name is never told to Lua. That means that this does not work: % fails, ColorA not known to Lua5 KB (722 words) - 13:46, 8 June 2020
- It was introduced in 2010 to reduce needed calls with lua. Source: https://mailman.ntg.nl/archives/list/ntg-context@ntg.nl/message/AIAWMGBFQQ5QPKNPOPDKFE4U3P4DZJDY/2 KB (233 words) - 12:53, 8 May 2024
- account when encapsulating Lua code. which normally result in a space are ignored and the spaces collapsed, so Lua4 KB (447 words) - 09:24, 7 August 2020