diff options
Diffstat (limited to 'doc/context/sources/general/manuals/luatex/luatex-enhancements.tex')
| -rw-r--r-- | doc/context/sources/general/manuals/luatex/luatex-enhancements.tex | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/doc/context/sources/general/manuals/luatex/luatex-enhancements.tex b/doc/context/sources/general/manuals/luatex/luatex-enhancements.tex index 5a2764f68..6b84570e8 100644 --- a/doc/context/sources/general/manuals/luatex/luatex-enhancements.tex +++ b/doc/context/sources/general/manuals/luatex/luatex-enhancements.tex @@ -463,7 +463,7 @@ node list interface, you may even end up with assertion errors from within the \stopsubsection -\startsubsection[title={\lpr {latelua}}] +\startsubsection[title={\lpr {latelua} and \lpr {lateluafunction}}] Contrary to \prm {directlua}, \lpr {latelua} stores \LUA\ code in a whatsit that will be processed at the time of shipping out. Its intended use is a cross @@ -482,7 +482,10 @@ Expansion of macros in the final \type {<general text>} is delayed until just before the whatsit is executed (like in \prm {write}). With regard to \PDF\ output stream \lpr {latelua} behaves as \PDF\ page literals. The \syntax {name <general text>} and \syntax {<16-bit number>} behave in the same way as -they do for \prm {directlua} +they do for \prm {directlua}. + +The \lpr {lateluafunction} primitive takes a number and is similar to \lpr +{luafunction} but gets delated to shipout time. It's just there for completeness. \stopsubsection |