From: "Patrick Gundlach" <patrick@gundla.ch>
Subject: Re: Problem with \defintion.
Date: 28 Nov 2004 19:56:00 +0100 [thread overview]
Message-ID: <m2sm6tzttr.fsf@levana.de> (raw)
In-Reply-To: <BAY23-F18708B5382257C6482D18FFBBC0@phx.gbl> (Dirar BOUGATEF's message of "Sun, 28 Nov 2004 15:41:44 +0000")
Hello Dirar,
> This is an example:
[this is what I mean with complete, but minimal example. The itemize
environment has nothing to do with the problem]
\definedescription [definition]
\starttext
\definition{HMV} blablabla
\definition{TTV} blablabla
% uncomment this to see the error
% \definition{QTV} blablabla
\stoptext
> l.360 \stopitemize
[this is the line number]
> I can now compile but the doc does talk about this!
I guess you meant to write "does not". If you do, than please have a
look at 10.2 again. All examples have a \par at the end (at least at a
quick glance). And an empty line as you had in your second description
is equivalent to \par. The description in texshow-web (and alike) is
incorrect. (<http://texshow.contextgarden.net/cmd=description>)
> Question: Do we have to put a \par.
Yes.
> It is really bizarre that it solves the problem, cause my items are
> defined far away in my document from the definitions.
What I think is more bizarre, that the problem did not already occur
with two \definition{...}.
Patrick
--
ConTeXt wiki: http://contextgarden.net
prev parent reply other threads:[~2004-11-28 18:56 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
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 [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=m2sm6tzttr.fsf@levana.de \
--to=patrick@gundla.ch \
--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).