On 4/7/24 22:33, Hans Hagen wrote:
No problem, is it a rpi 5? If so, how does that one perform?
Yes, it's a Pi 5 with 8GB of RAM, and I'm very satisfied with the
performance. I use it headless for backup, file serving, and the
occasional context job that ties the cpu up for a long time, and i
On 4/7/2024 10:14 PM, Thomas A. Schmitz wrote:
On 4/7/24 19:44, Hans Hagen wrote:
ok, so this "on" ... where does it come from .. you can try to run
with \tracingall and then quit the run after the first and search the
log for !on to get a clue
Hans
Found it - and I'm embarrassed to say it
On 4/7/24 19:44, Hans Hagen wrote:
ok, so this "on" ... where does it come from .. you can try to run with
\tracingall and then quit the run after the first and search the log for
!on to get a clue
Hans
Found it - and I'm embarrassed to say it was in my own environment file,
not in the lmtx
On 4/7/2024 7:37 PM, Thomas A. Schmitz wrote:
On 4/7/24 19:21, Hans Hagen wrote:
can you make a format with line 25 of context.mkxl uncommented to see
if you get a message (not production, just a test)
Hans
That should give a message "some spurious input in line..." in the
output or the log
On 4/7/24 19:21, Hans Hagen wrote:
can you make a format with line 25 of context.mkxl uncommented to see if
you get a message (not production, just a test)
Hans
That should give a message "some spurious input in line..." in the
output or the log, right? No, did not see such a message.
Thom
On 4/7/2024 7:08 PM, Thomas A. Schmitz wrote:
Hi everybody,
this is bizarre, but hear me out: a file that I have has a mixture of
xml, TeX and Lua. It compiles cleanly, no problem, on macos and linux. I
also have a little raspberry pi on which I have installed lmtx. The file
compiles, BUT: it
