ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Dirar BOUGATEF" <chabah5@hotmail.com>
Subject: Re: Problem with \defintion.
Date: Sun, 28 Nov 2004 15:41:44 +0000	[thread overview]
Message-ID: <BAY23-F18708B5382257C6482D18FFBBC0@phx.gbl> (raw)
In-Reply-To: <20041128152200.118@news.comp.lancs.ac.uk>

Hi Adam,

This is an example:

\starttext
\definition{HMV} blablabla
\definition{TTV} blablabla

%I also have items sometime afterwards:

\startitemize[r]
%
\head My head \par
\startitemize[triangle]
\item First Item
\item Second Item
\item Third Item
\stopitemize
%
\stopitemize
\stoptext

At this point, it compiles, but when i add a third definition, lets say 
\definition{QTV} blablabla

It generates the error:

! Undefined control sequence.
<write> ... \twopassentry {\s!list }{\currentlist
                                                  }{\currentlist 
:\noflistel...
<inserted text>
                }\endwrite
\immediatewriteutilitycommand ...ti {c \string #1}

\stopitemgroup ...th =\zerocount \dolistreference
                                                  \fi \iffirstlist \else 
\en...
l.360 \stopitemize

I have just tried \par after each definition as follows  \definition{QTV} 
blablabla \par

I can now compile but the doc does talk about this!

Question: Do we have to put a \par. It is really bizarre that it solves the 
problem, cause my items are defined far away in my document from the 
definitions.

  reply	other threads:[~2004-11-28 15:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-28 15:09 Dirar BOUGATEF
2004-11-28 15:22 ` Adam Lindsay
2004-11-28 15:41   ` Dirar BOUGATEF [this message]
2004-11-28 16:27     ` Patrick Gundlach
2004-11-28 18:00       ` Dirar BOUGATEF
2004-11-28 18:53         ` Matthias Weber
2004-11-28 19:18           ` Dirar BOUGATEF
2004-11-28 20:10             ` Patrick Gundlach
2004-11-28 21:17             ` h h extern
2004-11-28 20:48           ` h h extern
2004-11-28 18:56     ` Patrick Gundlach

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=BAY23-F18708B5382257C6482D18FFBBC0@phx.gbl \
    --to=chabah5@hotmail.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).