ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Marco Pessotto <melmothx@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: How to avoid that \writetolist becomes a page-breaker
Date: Tue, 14 Dec 2010 22:32:18 +0100	[thread overview]
Message-ID: <87wrnc3usd.fsf@universe.krase.net> (raw)
In-Reply-To: <8762uw5dm7.fsf@universe.krase.net>

Marco Pessotto <melmothx@gmail.com> writes:

> Probably due to my abuse of \writetolist, I noticed that inserting
> \writetolist right after \subject makes TeX to think that it can break
> the page there without problems.
>
> See the following minimal example:
>
> %===============cut here=============
>
> \definelist[myrandompart]
>
> \starttext
>
> \dorecurse{12}{
> \input reich 
> }
> \subject{\bf Wrong!}
> \writetolist[myrandompart]{It's a test}
>
> \input knuth
>
> \page
>
> \dorecurse{12}{
> \input reich 
> }
> \subject{\bf Correct!}
> %\writetolist[myrandompart]{It's a test}
>
> \input knuth
>
> %===============cut here=============
>
> I'm pretty sure the solution is out there.
> Some hints would be very welcome.
>
> Thanks in advance

To answer to my own question, it looks like that

\subject{\bf My title!}
\dontleavehmode
\writetolist[myrandompart]{}{It's a test}

works. The question if is this the right thing to do, still remains,
though

-- 
Marco

___________________________________________________________________________________
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:[~2010-12-14 21:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 20:00 Marco Pessotto
2010-12-14 21:32 ` Marco Pessotto [this message]
2010-12-15 11:40   ` Hans Hagen
2010-12-15 11:42 ` Hans Hagen
2010-12-15 11:47   ` Marco Pessotto

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=87wrnc3usd.fsf@universe.krase.net \
    --to=melmothx@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).