From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Jeong Dal <haksan@me.com>
Subject: Re: unwanted page break in contents
Date: Sun, 26 Aug 2018 17:17:19 +0200 [thread overview]
Message-ID: <144f95c1-7d1e-cbaf-9e37-e5e827d67f84@gmail.com> (raw)
In-Reply-To: <A28D046C-C709-46D6-A7B9-081DEE302A38@me.com>
Jeong Dal schrieb am 26.08.18 um 10:06:
> Hi,
>
> In the table of contents, there is a unwanted blank space after chapter 2.
> There is a page break if the remaining space is not enough to cover the list of the next chapter.
> For example, page break after ch 2. in the following example.
>
> Is it possible to list them continuously?
>
> Best regards,
>
> Dalyoung
>
> %%%%%%%%
> \starttext
> \definepagebreak[emptyodd][yes,header, footer, odd]
> \setuphead[chapter][page=emptyodd]
>
> \setuphead[title][incrementnumber=list]
> \setupcombinedlist[content][list={title,chapter,section,subsection}]
> \setuplist[chapter, title][width=5mm, style=,textcommand={\ss\bf }]
> \setuplist[section][width=10mm, style=,textcommand={\ss }]
\setuplist
[section]
[width=10mm,
style=,
textstyle=\ss,
after={\blank[preference]}]
Wolfgang
___________________________________________________________________________________
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:[~2018-08-26 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2541.1535153034.2042.ntg-context@ntg.nl>
2018-08-26 8:06 ` Jeong Dal
2018-08-26 15:17 ` Wolfgang Schuster [this message]
2018-08-26 15:24 ` Jeong Dal
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=144f95c1-7d1e-cbaf-9e37-e5e827d67f84@gmail.com \
--to=wolfgang.schuster.lists@gmail.com \
--cc=haksan@me.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).