summaryrefslogtreecommitdiff
path: root/systems/doc/luatex/luatex-tex.tex
diff options
context:
space:
mode:
authorNorbert Preining <norbert@preining.info>2020-03-15 03:01:24 +0000
committerNorbert Preining <norbert@preining.info>2020-03-15 03:01:24 +0000
commit87cddce361c3b477029d13b27bdaa57190b2d74b (patch)
tree0b8f15ef416645c1438cdc4228a1ddb44691b17c /systems/doc/luatex/luatex-tex.tex
parent942e56ba7d147d18d379305e76f064cec0aade7d (diff)
CTAN sync 202003150301
Diffstat (limited to 'systems/doc/luatex/luatex-tex.tex')
-rw-r--r--systems/doc/luatex/luatex-tex.tex36
1 files changed, 21 insertions, 15 deletions
diff --git a/systems/doc/luatex/luatex-tex.tex b/systems/doc/luatex/luatex-tex.tex
index 0924896288..4e70243c6d 100644
--- a/systems/doc/luatex/luatex-tex.tex
+++ b/systems/doc/luatex/luatex-tex.tex
@@ -113,18 +113,6 @@ checking some mechanism going haywire.
\stopsubsection
-\startsubsection[title={Code page (Windows only)}]
-
-\libindex{getcodepage}
-
-The \type {getcodepage} returns the value from \type{GetOEMCP()}
-(the current original equipment manufacturer (OEM) code page identifier for the operating system)
-and the value from \type{GetACP()} (the current Windows ANSI code page identifier for the operating system).
-
-\stopsubsection
-
-
-
\stopsection
\startsection[title={The \type {status} library}][library=status]
@@ -1488,6 +1476,23 @@ tex.runtoks(<lua function>)
When the \prm {tracingnesting} parameter is set to a value larger than~2 some
information is reported about the state of the local loop.
+This function has two optional arguments in case a token register is passed:
+
+\startfunctioncall
+tex.runtoks(<token register>,force,grouped)
+\stopfunctioncall
+
+Inside for instance an \type {\edef} the \type {runtoks} function behaves (at
+least tries to) like it were an \type {\the}. This prevents unwanted side
+effects: normally in such an definition tokens remain tokens and (for instance)
+characters don't become nodes. With the second argument you can force the local
+main loop, no matter what. The third argument adds a level of grouping.
+
+You can quit the local loop with \type {\endlocalcontrol} or from the \LUA\ end
+with \type {tex.quittoks}. In that case you end one level up! Of course in the
+end that can mean that you arrive at the main level in which case an extra end
+will trigger a redundancy warning (not an abort!).
+
\subsubsection{\type {forcehmode}}
\libindex{forcehmode}
@@ -1952,15 +1957,16 @@ and|/|or console.
\libindex{write}
\startfunctioncall
-texio.write(<string> target, <string> s, ...)
+texio.write(<string> target | <integer> stream, <string> s, ...)
texio.write(<string> s, ...)
\stopfunctioncall
Without the \type {target} argument, writes all given strings to the same
location(s) \TEX\ writes messages to at this moment. If \prm {batchmode} is in
effect, it writes only to the log, otherwise it writes to the log and the
-terminal. The optional \type {target} can be one of three possibilities: \type
-{term}, \type {log} or \type {term and log}.
+terminal. The optional \type {target} can be one of four possibilities: \type
+{term}, \type {log}, \type {term and log} or a valid integer of a stream
+opened for writing.
Note: If several strings are given, and if the first of these strings is or might
be one of the targets above, the \type {target} must be specified explicitly to