ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jose Luis Diaz <jldiaz@telecable.es>
Cc: ConTeXt Mailing List <ntg-context@ntg.nl>
Subject: Re[3]: Q: Keeping blocks together. New problems
Date: Thu, 25 Oct 2001 18:29:31 +0200	[thread overview]
Message-ID: <91190862830.20011025182931@telecable.es> (raw)
In-Reply-To: <5.1.0.14.1.20011025140917.032f0330@server-1>

Hello Hans,

El jueves, 25 de octubre de 2001, a las 14:10, Hans dijo:

Hans>             before={\page[no]}

I  also  thought  that,  but  still  keep getting wrong page breaks. I
suppossed that maybe the problem was an obsolete ConTeXt version, so I
downloaded  the  latest  from  www.ntg.nl,  and re-created the cont-en
format. Still wrong page breaks.

I  also  tried  the new columnset environment which you suggested, but
context  stops  with  the fatal error: No room for a new box (which is
generated  from  Plain).  I  guess  that  the  problem is perhaps some
infinite  loop,  since  the error message also spits out several lines
containing \dodorecurse and similar things.

But  the real problems appeared when I discovered that I was unable to
compile  some  previous  work  which  compiled  fine  with my previous
ConTeXt. Fortunately I was able to trace down the command which caused
the trouble, and provisionally I suppresed it from my source.

However,  I would like to know if something was wrong with my command,
or  if it is a bug in the new ConTeXt version. What I was trying to do
was  to  typeset  the  numbers  in  a  different  color/typeface in an
enumerated  environment.  I  was  unable  to  find  which parameter of
\setupitemize  would  serve  that  purpose,  so  I decided to create a
"conversion" for doing the job. This is what I wrote:

\defineconversion[cn][\colorednumber]
\def\colorednumber#1{\color[red]{\bf{\numbers{#1}}}

\startitemize[cn,inmargin]
\item One
\item Two
\stopitemize

But I get the following error message:

 |! Undefined control sequence.
 |\do\groupedcommand ...f \dogroupedcommand
 |                                          {\ifx \next \bgroup \def \\...
 |\colornumero #1->\color [white]
 |                               {\bf \numbers {#1}}
 |\dolistitem ...mbool \s!local \itemlevel }
 |                                          }\kopsomfalse \subsomfalse ...
 |\complexdosom ...ignorespaces \dolistitem
 |                                          \ifpackeditems \stelwitruim...
 |<to be read again>
 |                   O
 |l.127   \item O
 |               ne

The  trick  worked  fine  with  the  previous  ConTeXt version. What's
happening?

Thanks again, and sorry for all these problems I'm posing.

-- 
Regards,
 Jose                            mailto:jldiaz@telecable.es


      reply	other threads:[~2001-10-25 16:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-25  8:45 Q: Keeping blocks together Jose Luis Diaz
2001-10-25  9:54 ` Hans Hagen
2001-10-25 11:20   ` Re[2]: " Jose Luis Diaz
2001-10-25 12:10     ` Hans Hagen
2001-10-25 16:29       ` Jose Luis Diaz [this message]

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=91190862830.20011025182931@telecable.es \
    --to=jldiaz@telecable.es \
    --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).