Radhelorn wrote:
\getparameters[\??dd#1]
[\s!do\c!state=\v!stop,\s!do\c!command=\normal@@descriptionhandler,\c!level=,#2]%
-
\doifvalue{\??dd#1\c!location}\v!top{\doassign[\??dd#1][\c!inbetween=\blank]}%
+ \doifvalue{\??dd#1\c!location}\v!top{%
+
\doifnotvalue{\??dd#1\c
Christopher Creutzig wrote:
Radhelorn wrote:
I mean parameter values. Then why not have ConTeXt add braces to every
parameter? Or there will be slowdown Taco mentioned?
Exactly. ConTeXt would need to find out the parameters' boundaries
first, and that is the place where things would becom
Radhelorn wrote:
I mean parameter values. Then why not have ConTeXt add braces to every
parameter? Or there will be slowdown Taco mentioned?
Exactly. ConTeXt would need to find out the parameters' boundaries
first, and that is the place where things would become slow, since it is
not possi
Radhelorn said this at Thu, 14 Jul 2005 21:25:50 +0400:
>> If you think of the braces as "quoting" the parameter values, you'll
>> probably be alright.
>
>I mean parameter values. Then why not have ConTeXt add braces to every
>parameter? Or there will be slowdown Taco mentioned?
Sort of. That, I
Adam Lindsay wrote:
Taco Hoekwater said this at Thu, 14 Jul 2005 16:30:10 +0200:
So every command with brackets needs to be grouped? Maybe something
else? Where to look at it?
I know of nothing else, just brackets. Any bracket, not just as
part of a command, but also in cases like this:
\s
Taco Hoekwater said this at Thu, 14 Jul 2005 16:30:10 +0200:
>> So every command with brackets needs to be grouped? Maybe something
>> else? Where to look at it?
>
>I know of nothing else, just brackets. Any bracket, not just as
>part of a command, but also in cases like this:
>
> \setuppublica
Radhelorn wrote:
Thanks.
So every command with brackets needs to be grouped? Maybe something
else? Where
to look at it?
It's better grouping with {} with brackets; there should be nothing else.
luigi
___
ntg-context mailing list
ntg-context@n
Radhelorn wrote:
Thanks.
So every command with brackets needs to be grouped? Maybe something
else? Where to look at it?
I know of nothing else, just brackets. Any bracket, not just as
part of a command, but also in cases like this:
\setuppublications[left={[}]
Taco
Taco Hoekwater wrote:
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 eve
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 intentiona
Hello All!
I think that I've found a bug in descriptions. It seems that it is
impossible to redefine inbetween option -- it always produces a \blank.
Try this:
\definedescription[desc][before=before,after=after,inbetween=inbetween,location=top]
\desc{test} test
I've fixed it this way:
--- core-
11 matches
Mail list logo
