From: Zenlima <post@zenlima.eu>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: [***SPAM***] unwanted space and error in combination of writebetweenlist and placecontent[criterium= local]
Date: Mon, 13 May 2013 02:00:44 +0200 [thread overview]
Message-ID: <20130513020044.4ec9c721@zenlima.eu> (raw)
Hi,
I ran into one error and one problem during building a part as two
columns into the toc.
1. Extra line: I am getting an unwanted extra empty line at the bottom
of two columns with an even number of total lines - with an odd
number of total lines no extra empty line appears. How can I get rid
of it? (see attached example)
2. This error only appears only with \placecontent[criterium=local] in
combination with a beginning line of \writebetweenlist; with a global
\placecontent and \writebetweenlist it works fine. To reproduce this
uncomment the line "%\placecontent[criterium=local]" in the attached
example.
(Sorry that I was not able to make the example shorter, I needed some
"meat" to fill the toc for the showcases)
Thanks,
H.
--8<----------------------------
\usemodule[subsub]
\definehead[paragraphHead][alternative=myheader,section=section-8,number=no]
\defineheadalternative
[myheader]
[alternative=horizontal,
renderingsetup=setup:myheader]
\startsetups [setup:myheader]
\inouter{\headtextcontent}
\stopsetups
\setuplist[chapter][style=bold,before=\blank,alternative=b,width=1.5em,color=HeadColor]
\setuplist[section][margin=1.5em,width=2em]
\setuplist[subsection][margin=3.5em,width=3em]
\setuplist[paragraphHead][alternative=c,style=\tfx]
\def\startParagraphTocColumns{%
\writebetweenlist[paragraphHead][location=here]{\setupnarrower[left=2em]\startnarrower[left]\startcolumns[n=2,distance=0mm,balance=yes]}%
\ignorespaces}
\def\stopParagraphTocColumns{%
\writebetweenlist[paragraphHead][location=here]{\stopcolumns\stopnarrower}%
\ignorespaces}
\starttext
\setupcombinedlist[content][list={chapter,section,subsection,textdividerHead,paragraphHead}]
\completecontent
\startParagraphTocColumns
\dorecurse{5}{\paragraphHead{Hasselt makes headlines}
\input tufte}
\stopParagraphTocColumns
\chapter{Lorem ipsum}
\section{Sed eram}
\chapter{Lorem ipsum}
%\placecontent[criterium=local]
\section{Sed eram}
\section{Sed eram}
\startParagraphTocColumns
\dorecurse{5}{\paragraphHead{Hasselt makes headlines}
\input tufte}
\stopParagraphTocColumns
\section{Sed eram}
\section{Sed eram}
\startParagraphTocColumns
\dorecurse{4}{\paragraphHead{Hasselt makes headlines}
\input tufte}
\stopParagraphTocColumns
\section{Sed eram}
\startParagraphTocColumns
\dorecurse{3}{\paragraphHead{Hasselt makes headlines}
\input tufte}
\stopParagraphTocColumns
\section{Sed eram}
\section{Sed eram}
\stoptext
___________________________________________________________________________________
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 other threads:[~2013-05-13 0:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130513020044.4ec9c721@zenlima.eu \
--to=post@zenlima.eu \
--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).