ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: John Culleton <john@wexfordpress.com>
Subject: Pesky sidebars.
Date: Wed, 8 May 2002 17:17:42 -0400	[thread overview]
Message-ID: <200205081717.42337.john@wexfordpress.com> (raw)

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


             reply	other threads:[~2002-05-08 21:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-08 21:17 John Culleton [this message]
2002-05-09  8:54 ` Patrick Gundlach
2002-05-09 13:17   ` OT: maps23 emacs/auctex article Idris Samawi Hamid
2002-05-09 14:10     ` Taco Hoekwater
2002-05-09 23:12 ` Pesky sidebars Hans Hagen
2002-05-10 13:51   ` John Culleton
2002-05-10 17:16     ` Hans Hagen
2002-05-10 19:57       ` John Culleton
2002-05-11  9:11         ` Hans Hagen
2002-05-11 10:19         ` Re[2]: " Giuseppe Bilotta
2002-05-13 19:22           ` John Culleton
2002-05-13 21:29             ` Re[4]: " Giuseppe Bilotta
2002-05-14 15:41               ` John Culleton
2002-05-11  4:36       ` Drop words, Drop boxes Idris Samawi Hamid
2002-05-11 13:03         ` Hans Hagen

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=200205081717.42337.john@wexfordpress.com \
    --to=john@wexfordpress.com \
    /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).