I'm having trouble understanding space inserted around itemize and
TABLE objects.  I found some great advice from the mailing list
archives, and managed to cobble together a setup that *almost* works.
Now I have only two problems.  I welcome any help.

First: In the example below, the word "monkey" creates no vertical
space---even if it's commented out, there's no change in the space
between "Title" and "alpha".  I'd like to tighten that space up---I've
been resorting to \vskip{-10ex}, but surely there's a way to not put
that space there in the first place.  I'm already using
packed,intro,joinedup for the itemize in an attempt to shove it as
high as possible; is there another way?

Second: in the same example, the "Second" subject does not appear.
Uncommenting the llama doesn't make any surprising difference (well,
it moves the table down, showing that tables don't have the
space-filling property of itemizes), but uncommenting the apricot does
cause the "Second" subject to appear.  How can I force the "Second"
subject to appear next to the table?

Thank you for any help.

\setuphead[subject][alternative=text,distance=0pt,command=\MyHead]
\setupinmargin[style=\setupinterlinespace]
\def\MyHead#1#2{\margintitle[low]{\rotate{#1 #2}}}

\setupitemize[packed,intro,joinedup,KR]

\starttext
\title{Title}

\subject{First}

monkey

\startitemize[columns]
\item alpha
\item beta
\item gamma
\stopitemize


\subject{Second}

%llama

\bTABLE
\bTR \bTD One \eTD \eTR
\eTABLE

\stoptext



-- 
Brian Sniffen
http://evenmere.org/~bts/
<b...@evenmere.org>
___________________________________________________________________________________
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Reply via email to