From: Duncan Hothersall <dh@capdm.com>
Subject: Re: TABLE in item
Date: Sun, 29 Oct 2006 13:23:21 +0000 [thread overview]
Message-ID: <4544AB49.8040607@capdm.com> (raw)
In-Reply-To: <mailman.1.1162119602.3415.ntg-context@ntg.nl>
> \let\beforeTABLEsplitbox\relax
> \let\afterTABLEsplitbox \relax
> \let\beforeTABLEbox \relax
> \let\afterTABLEbox \relax
>
> you can play with these macros since they are the formal hooks
Hans,
I played with
\let\beforeTABLEsplitbox\dontleavehmode
\def\afterTABLEsplitbox{\relax\dontleavehmode}
\let\beforeTABLEbox\dontleavehmode
\let\afterTABLEbox\relax
which gives the right indents but stops the tables splitting.
I think I will just have to live with non-splitting tables for now,
unless you can suggest a better redefinition?
Thanks very much for the help anyway.
Duncan
next parent reply other threads:[~2006-10-29 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1162119602.3415.ntg-context@ntg.nl>
2006-10-29 13:23 ` Duncan Hothersall [this message]
[not found] <mailman.1.1161943202.25312.ntg-context@ntg.nl>
2006-10-27 10:28 ` Duncan Hothersall
2006-10-28 11:07 ` Hans Hagen
2006-10-27 9:53 Duncan Hothersall
2006-10-28 11:04 ` 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=4544AB49.8040607@capdm.com \
--to=dh@capdm.com \
--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).