From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/7829
Path: main.gmane.org!not-for-mail
From: John Culleton <john@wexfordpress.com>
Newsgroups: gmane.comp.tex.context
Subject: Pesky sidebars.
Date: Wed, 8 May 2002 17:17:42 -0400
Sender: owner-ntg-context@let.uu.nl
Message-ID: <200205081717.42337.john@wexfordpress.com>
NNTP-Posting-Host: coloc-standby.netfonds.no
Mime-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 8bit
X-Trace: main.gmane.org 1035398273 22671 80.91.224.250 (23 Oct 2002 18:37:53 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Wed, 23 Oct 2002 18:37:53 +0000 (UTC)
Original-To: ntg-context@ntg.nl
Xref: main.gmane.org gmane.comp.tex.context:7829
X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:7829

On some pages sidebars work fine, on others they have a white line
through the background, and on still others an overflow problem stalls
the entire compile. You have to kill the window or session to get out of it.
Here is a sidebar that works fine:

\startmarginblock
\setuptolerance[horizontal,tolerant]
\startbackground
Using Context text can be placed in the margin using a margin block.
A background can also be added.
\stopbackground
\stopmarginblock

But here is a much shorter one that stalls the system.
\startmarginblock
\setuptolerance[horizontal,tolerant]
\startbackground
WYSIWIG
can slow
you down.
\stopbackground
\stopmarginblock

I cannot see anything radically different about the context (Small c :)
that would cause these problems. 

I have tried \starttyping & stoptyping but they seem to have littel
effect either way.

Is there something wrong with my overall approach?

John Culleton
-- 
Able Indexers and Typesetters
http://wexfordpress.com