Hello,
today I updated ConTeXt to the version of 2019-03-05.
While testing a type-script I got an error, when I ask for the font name.
lua error > lua error on line 1 in file /test.tex:
...ext/tex/texmf-context/tex/context/base/mkiv/font-syn.lua:519: bad argument
#1 to 'lower' (string
On Fri, 08 Mar 2019 17:05:02 +0100
Procházka Lukáš Ing. wrote:
> is it possible (namely for debugging) values of MP variables (be it on the
> console or in the log)?
>
> I thought there is MP command "show" (mentioned in mpman.pdf) for this
message(pt) ;
puts it into the (context) log.
show
Am Fri, Mar 08, 2019 at 03:43:20PM + schrieb Ursula Hermann:
> Dear List!
>
> I have the following example:
>
> \defineframedtext
> [prettyblock]
> [width=10cm,
>indenting={yes, small},
>background=color, backgroundcolor=lightgreen,
>foreground=color, foregroundcolor=black ,
Hello,
is it possible (namely for debugging) values of MP variables (be it on the
console or in the log)?
I thought there is MP command "show" (mentioned in mpman.pdf) for this; but:
\starttext
A
\startMPcode
newpair pt; pt := (10,20);
show pt; % <-- How
Dear List!
I have the following example:
\defineframedtext
[prettyblock]
[width=10cm,
indenting={yes, small},
background=color, backgroundcolor=lightgreen,
foreground=color, foregroundcolor=black ,
offset=2mm,
align=flushleft]
My problem is now:
how can I write, if I have an
Hello,
I encountered the same with the minimal:
\starttext
\nonexisting
\stoptext
Messages displayed on the console are "full-fledged" both with "--ansi" switch
or without it.
But the resulting .log file is incomplete with "--ansi".
Would it be possible to adapt loggers to write
