ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: h h extern <pragma@wxs.nl>
Subject: Re: Re: Learning ConTeXt, typical hurdle
Date: Sun, 13 Mar 2005 22:42:16 +0100	[thread overview]
Message-ID: <4234B3B8.4050504@wxs.nl> (raw)
In-Reply-To: <m2oedrfsky.fsf@levana.de>

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 whitespace before a command frightens me.
> 
> 
> Just the way it works :-) Nothing to worry about.

there are only a few commands that depend on that

for descriptions, you can also use

\startwhatever {...}

\stopwhatever

in addition to

\whatever {...} ... \par

given that you defined whatever -)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------

      parent reply	other threads:[~2005-03-13 21:42 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
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 [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=4234B3B8.4050504@wxs.nl \
    --to=pragma@wxs.nl \
    --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).