From: "Dirar BOUGATEF" <chabah5@hotmail.com>
Subject: Re: Re: Problem with \defintion.
Date: Sun, 28 Nov 2004 19:18:27 +0000 [thread overview]
Message-ID: <BAY23-F28643C2EDA1D4B50D6040BFBBC0@phx.gbl> (raw)
In-Reply-To: <D4A3CEF4-416E-11D9-AC81-000A959AFACC@indiana.edu>
Thanks to you all,
\par solves the problem as i said. A blank line does obviously the same
thing.
The documentation has only 2 explicit examples and no \par is used within (I
assume a blank line was used instead). The box where the command is defined
specifies the \par argument which isn't obvious to see because there is a
mistake (\description appears instead of \definition which can be
confusing).
Still don't know why it worked with 2 \definitions but anyway, i know my
error now :)
Bye.
Dirar.
next prev parent reply other threads:[~2004-11-28 19:18 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 [this message]
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-F28643C2EDA1D4B50D6040BFBBC0@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).