Gerben Wierda wrote:
Apart from adapting, the \startitemize \stopitemize does not require me
to have a \par at the end. That is also confusing.
That's because it's a different construct (less variants in visualization
and
such);
I understand that, but for someone new to ConTeXt, the
Hi Gerben,
Due to a mistaken handling you roriginal mail I lost it :-(
In that mail in the last part, I believe it was an example \component I
saw, that you said \starttext ... \stoptext. You do not need this pair,
The handling of starting and stopping is done by the \startproject ...
Patrick Gundlach wrote:
Hey Gerben,
Now what turns out to solve this? Empty lines before \description and
\stopdescriptions
Things that were defined using \definedescription rely on \par as a
delimiter.
Though I like ConTeXt if I look at certain design aspects, behaviour that
depends on
On 13 Mar 2005, at 23:27, h h extern wrote:
Gerben Wierda wrote:
Hey Gerben,
Now what turns out to solve this? Empty lines before \description
and
\stopdescriptions
Things that were defined using \definedescription rely on \par as a
delimiter.
Though I like ConTeXt if I look at certain design
Hey Gerben,
Now what turns out to solve this? Empty lines before \description and
\stopdescriptions
Things that were defined using \definedescription rely on \par as a
delimiter.
Though I like ConTeXt if I look at certain design aspects, behaviour that
depends on whitespace before a command
Hey Gerben,
Now what turns out to solve this? Empty lines before \description and
\stopdescriptions
Things that were defined using \definedescription rely on \par as a
delimiter.
Though I like ConTeXt if I look at certain design aspects, behaviour
that
depends on whitespace before a
Hello Gerben,
[...]
Things that were defined using \definedescription rely on \par as a
delimiter.
What this introduces is that the working of the ascii file depends on its
layout.
I completely agree with you here. This description - \par thing has
been on the mailinglist a couple
