From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Marco Pessotto <melmothx@gmail.com>
Subject: Re: How to avoid that \writetolist becomes a page-breaker
Date: Wed, 15 Dec 2010 12:40:56 +0100 [thread overview]
Message-ID: <4D08A948.2020908@wxs.nl> (raw)
In-Reply-To: <87wrnc3usd.fsf@universe.krase.net>
On 14-12-2010 10:32, Marco Pessotto wrote:
>
> \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
it's quite ok as long as you realize that it introduces 'something' in
the text stream, so
xxx
\dontleavehmode\writetolist[myrandompart]{}{It's a test}
xxx
is actually:
xxx
[something written to a list]
xxx
so when whitespace is setup, in some cases you can get some extra
also, the [something ...] can end up on the current page or the next
one, depending on the circumstances
in practice it's no real problem as one will do explicit writes inside
boxes or so
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-12-15 11:40 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
2010-12-15 11:40 ` Hans Hagen [this message]
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=4D08A948.2020908@wxs.nl \
--to=pragma@wxs.nl \
--cc=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).