On 5/31/2021 12:36 PM, Werner Hennrich wrote:
Hello Hans,
loading from cont-loc now works, thank you!
Am 31.05.21 um 11:33 schrieb Hans Hagen:
you can wrap such a patch in:
\ifcsname\??xtableflushsplit\v!repeat\endcsname \else
\fi
to make sure that it's not overloading something built in
sorry, not true:
Am 31.05.21 um 12:36 schrieb Werner Hennrich:
but the patch isn't loaded any more.
my
\writestatus\m!system{beware: LOCAL PATCH LOADED FOR xtable}
from inside the \else to \fi is indeed still in my console.
case re safe update closed -
thanks, Werner
Hello Hans,
loading from cont-loc now works, thank you!
Am 31.05.21 um 11:33 schrieb Hans Hagen:
you can wrap such a patch in:
\ifcsname\??xtableflushsplit\v!repeat\endcsname \else
\fi
to make sure that it's not overloading something built in
if I do this, I get:
suggestion > use
On 5/31/2021 10:50 AM, Werner Hennrich wrote:
I still rely in all my installations on this bit at the bottom to be in
cont-new.mkxl.
Is there a way to make this patch update-safe?
There are comments
in ./tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl:
%D This file is loaded at
I still rely in all my installations on this bit at the bottom to be in
cont-new.mkxl.
Is there a way to make this patch update-safe?
There are comments
in ./tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl:
%D This file is loaded at runtime, thereby providing an excellent
place for
Am 25.04.21 um 10:52 schrieb Wolfgang Schuster:
Yes, some slack is needed to avoid the table being pushed to the next
space because not enough space is available. I recommend also to
ensure a minimum amount of space (e.g. 5 lines) is available to avoid
tables with just a few rows.
Wolfgang
I
Thank you Hans,
this works well in my unchanged MWE -
I'll do some more rigorous testing on monday and let you know.
Thanks a lot and hava a nice weekend!
Werner
Am 23.04.21 um 21:28 schrieb Hans Hagen:
Always tricky this (on my agenda is to look into the engines page
builder ...)
You can
On 4/23/2021 11:33 AM, Werner Hennrich wrote:
Hello everyone,
I'm having an xtable spanning several pages and need to have its headers
repeated.
For this I've set "split=repeat", but unfortunately this causes the
table to start with a new new page leaving the rest of the preceding
page
Hello everyone,
I'm having an xtable spanning several pages and need to have its headers
repeated.
For this I've set "split=repeat", but unfortunately this causes the
table to start with a new new page leaving the rest of the preceding
page empty. Having "split=yes" makes the tabe continue on