From: Werner Hennrich <wehe@gmx.at>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: new page before xtable with repeated headers
Date: Mon, 31 May 2021 10:50:58 +0200 [thread overview]
Message-ID: <4848a3d4-89c3-81ab-7ec9-cab83e399435@gmx.at> (raw)
In-Reply-To: <a8160df5-e5d2-3643-0118-25ae3062719a@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1343 bytes --]
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 hacks,
%D patches, extensions and new features. There can be local
overloads in cont-loc
%D (which has always been the case) and experimental code in
cont-exp (which is also
%D so old that I need to remind myself to check it occasionally, so
here is the
%D reminder).
I tried the mentioned local overload methods but didn't get them to work.
Did I mess up somehow or is the comment above outdated?
Are there any better ways - update-safe though?
Thanks a lot, Werner
Am 23.04.21 um 21:28 schrieb Hans Hagen:
> You can put this on cont-new.mkxl as test:
>
> \unprotect
>
> \defcsname\??xtableflushsplit\v!repeat\endcsname
> {\doloop
> {\clf_x_table_flush
> method {\v!split}%
> height
> \ifdim\pagegoal=\maxdimen\textheight\else\dimexpr\pagegoal-\pagetotal\relax\fi
> \relax
> \ifcase\c_tabl_x_state
> \exitloop
> \else
> \page
> \fi}}
>
> \protect
[-- Attachment #1.2: Type: text/html, Size: 2618 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2021-05-31 8:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 9:33 Werner Hennrich
2021-04-23 19:28 ` Hans Hagen
2021-04-24 7:56 ` Werner Hennrich
[not found] ` <97b89634-8d32-db43-ec9f-2fca501b9464@gmail.com>
2021-04-26 13:36 ` Werner Hennrich
2021-05-31 8:50 ` Werner Hennrich [this message]
2021-05-31 9:33 ` Hans Hagen
2021-05-31 10:36 ` Werner Hennrich
2021-05-31 10:45 ` Werner Hennrich
2021-05-31 12:07 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4848a3d4-89c3-81ab-7ec9-cab83e399435@gmx.at \
--to=wehe@gmx.at \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).