ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Radhelorn <radhelorn@mail.ru>
Subject: Not possible to redefine inbetween in \definedescription
Date: Thu, 14 Jul 2005 15:43:14 +0400	[thread overview]
Message-ID: <42D64FD2.5080104@mail.ru> (raw)

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-des.tex.orig   2005-06-14 06:56:00.000000000 +0400
+++ core-des.tex        2005-07-14 15:26:20.000000000 +0400
@@ -372,7 +372,8 @@
        \c!indenting,\c!indentnext,\c!align,\c!text,\c!distance,\c!command]%
     \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!inbetween}{\doassign[\??dd#1][\c!inbetween=\blank]}}%
     \setvalue        {#1}{\dodoubleempty\@@description[#1]}%
     \setvalue{\e!start#1}{\dodoubleempty\@@startdescription[#1]}%
     \setvalue{\e!stop #1}{\@@stopdescription{#1}}}%


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?


Thanks for your time.

-- 
Radhelorn <radhelorn@mail.ru>

             reply	other threads:[~2005-07-14 11:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-14 11:43 Radhelorn [this message]
2005-07-14 12:45 ` Taco Hoekwater
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=42D64FD2.5080104@mail.ru \
    --to=radhelorn@mail.ru \
    --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).