From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Not possible to redefine inbetween in \definedescription
Date: Thu, 14 Jul 2005 14:45:45 +0200 [thread overview]
Message-ID: <42D65E79.7080006@elvenkind.com> (raw)
In-Reply-To: <42D64FD2.5080104@mail.ru>
Hi,
Radhelorn wrote:
> ... [bug and fix snipped] ..
Thanks for the bug report.
> And when using commands with brackets in argumets like:
>
> \definedescription[desc][before=\blank[small]]
>
> ConTeXt will give many errors, so arguments needs to be grouped
> (before={\blank[small]}). Is this intentional?
Yes, that is a speed optimization. ConTeXt does not even attempt
to balance the occurrence of [ and ] at top-level, so the explicit
grouping indeed required.
It would be easy to extend ConTeXt to do this, but the speed
penalty would be substantial.
Greetings, Taco
next prev parent reply other threads:[~2005-07-14 12:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 11:43 Radhelorn
2005-07-14 12:45 ` Taco Hoekwater [this message]
2005-07-14 13:53 ` Radhelorn
2005-07-14 14:30 ` Taco Hoekwater
2005-07-14 15:08 ` Adam Lindsay
2005-07-14 17:25 ` Radhelorn
2005-07-14 17:27 ` Adam Lindsay
2005-07-14 17:49 ` Christopher Creutzig
2005-07-15 5:13 ` Radhelorn
2005-07-14 15:01 ` luigi.scarso
2005-07-20 19:58 ` Hans Hagen
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=42D65E79.7080006@elvenkind.com \
--to=taco@elvenkind.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).