From: Taco Hoekwater <taco@elvenkind.com>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: SOLVED Re: \bTABLE bug, please help !
Date: Tue, 10 Mar 2020 16:43:47 +0100 [thread overview]
Message-ID: <D779E152-1DF6-4E73-9BFF-83AC2BE8FA6B@elvenkind.com> (raw)
In-Reply-To: <6f568ec6-50dd-e55e-cf9b-9934e4903ce8@xs4all.nl>
> On 10 Mar 2020, at 16:20, Hans Hagen <j.hagen@xs4all.nl> wrote:
>
> On 3/10/2020 3:07 PM, Taco Hoekwater wrote:
>> Hi,
>> Never mind, I got it (starting at \loggingall output for a while). This
>> patch to my input fixes it:
>> \unprotect
>> \setupfootertexts[{\tabl_ntb_next_level \getbuffer[mytable] \tabl_ntb_prev_level}]
>> \protect
>
> you beat me on this ... (still puzzled because nesting shoudl kind of work)
Well, they are not _really_ nested, which is the problem, of course.
> I'll add this:
>
> %D This is for the special cases where for instance a table is in a header or footer
> %D line and we have a split table in progress. (See mail to list from Taco.)
>
> \unexpanded\def\bTABLEnested{\tabl_ntb_next_level\bTABLE}
> \unexpanded\def\eTABLEnested{\eTABLE\tabl_ntb_next_level}
That last macro should be \tabl_ntb_prev_level ;)
Taco
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2020-03-10 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 13:47 Taco Hoekwater
2020-03-10 14:07 ` SOLVED " Taco Hoekwater
2020-03-10 15:20 ` Hans Hagen
2020-03-10 15:43 ` Taco Hoekwater [this message]
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=D779E152-1DF6-4E73-9BFF-83AC2BE8FA6B@elvenkind.com \
--to=taco@elvenkind.com \
--cc=j.hagen@xs4all.nl \
--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).