From: "Patrick Gundlach" <patrick@gundla.ch>
Subject: Re: Learning ConTeXt, typical hurdle
Date: 10 Mar 2005 16:06:53 +0100 [thread overview]
Message-ID: <m2oedrfsky.fsf@levana.de> (raw)
In-Reply-To: <60028.213.84.141.31.1110461682.squirrel@213.84.141.31> (Gerben Wierda's message of "Thu, 10 Mar 2005 14:34:42 +0100 (CET)")
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 frightens me.
Just the way it works :-) Nothing to worry about.
Patrick
--
ConTeXt wiki: http://contextgarden.net
next prev parent reply other threads:[~2005-03-10 15:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 13:34 Gerben Wierda
2005-03-10 15:06 ` Patrick Gundlach [this message]
2005-03-10 16:09 ` Gerben Wierda
2005-03-10 17:05 ` Patrick Gundlach
2005-03-13 22:27 ` h h extern
2005-03-14 6:44 ` Gerben Wierda
2005-03-14 8:32 ` Hans Hagen
2005-03-14 10:28 ` Gerben Wierda
2005-03-10 17:52 ` Willi Egger
2005-03-13 21:42 ` h h extern
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=m2oedrfsky.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).