From: Thangalin <thangalin@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Blank page inserted when text reaches column's end
Date: Mon, 9 Dec 2019 18:37:17 -0800 [thread overview]
Message-ID: <CAANrE7rKqKJJteFPNK7zNG6LUmP33OhCHBQFwqBk=_Kh4MqbLQ@mail.gmail.com> (raw)
In-Reply-To: <fb89463a-9b47-0a61-2b71-97832eeee73b@gmail.com>
Thank you both. Neither approach removes the blank page with either
version 2019.06.11 or 2019.12.06 on Linux. Is there a specific version
of ConTeXt required? The code to generate the document resembles:
\setuppagenumbering[alternative=doublesided,page=no]
\installpagebreakhandler{last}{}
\setuplayout[grid=yes]
\starttext
\startcolumnset[n=2]
\input knuth \input lorem \input lorem \input knuth
\dorecurse{3}{No TV and no beer make Homer something something.}
\stopcolumnset
\stoptext
The second page remains, regardless of doublesided/singlesided or
pagebreakhandler.
Henri Menke pointed out that "page-cst.mkiv" contains an explicit line
break associated with stoppagegrid:
https://github.com/contextgarden/context-mirror/blob/f74c4055713ab52a11d12435eb04040ec6553129/tex/context/base/mkiv/page-cst.mkiv#L199-L201
Could this be grid itself be problematic?
Cheers!
___________________________________________________________________________________
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:[~2019-12-10 2:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-08 23:44 Thangalin
2019-12-09 8:41 ` Denis Maier
2019-12-09 17:23 ` Wolfgang Schuster
2019-12-10 2:37 ` Thangalin [this message]
2019-12-11 1:51 ` Thangalin
2019-12-11 4:55 ` Wolfgang Schuster
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='CAANrE7rKqKJJteFPNK7zNG6LUmP33OhCHBQFwqBk=_Kh4MqbLQ@mail.gmail.com' \
--to=thangalin@gmail.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).