ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <pragma@wxs.nl>
Subject: Re: \definenamespace
Date: Fri, 19 Nov 2010 18:35:14 +0100	[thread overview]
Message-ID: <12CE99E6-0C02-4194-B352-4D42485AF13C@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1011181951280.1909@ybpnyubfg.ybpnyqbznva>


Am 19.11.2010 um 02:05 schrieb Aditya Mahajan:

> I am not sure how this is supposed to work. Consider this example:
> 
> [...]

There is a bug in the code for the \define... commands, you need this definition for \doinstalldefinehandler:

\unexpanded\def\doinstalldefinehandler#1#2#3#4#5#6#7%
  {\unexpanded\def#2{\dodoubleempty#5}%
   \newtoks#6%
   \newtoks#7%
   \def#5[##1][##2]%
     {\edef#4{##1}%
      \the#6% predefine
      \ifsecondargument
        \doifassignmentelse{##2}
          {\getparameters[#1#4][\s!parent=#3,##2]}
          {\getparameters[#1#4][\s!parent=#1##2]}%
      \fi
      \the#7}}

To have three arguments for the \define... commands like \defineenumeration change the above command to:

\unprotected\unexpanded\def\doinstalldefinehandler#1#2#3#4#5#6#7%
  {\unexpanded\def#2{\dotripleempty#5}%
   \newtoks#6%
   \newtoks#7%
   \def#5[##1][##2][##3]%
     {\edef#4{##1}%
      \the#6% predefine
      \ifsecondargument
        \doifassignmentelse{##2}
          {\getparameters[#1#4][\s!parent=#3,##2]}
          {\getparameters[#1#4][\s!parent=#1##2,##3]}%
      \fi
      \the#7}}

Wolfgang

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2010-11-19 17:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-14 23:16 The visual counter module Aditya Mahajan
2010-11-15  9:37 ` Hans Hagen
2010-11-16 19:01 ` Mathieu Boespflug
2010-11-17 19:10 ` Philipp Gesang
2010-11-17 21:53   ` \definenamespace (was: The visual counter module) Wolfgang Schuster
2010-11-18  0:36     ` Philipp Gesang
2010-11-18  3:56       ` Wolfgang Schuster
2010-11-18  9:02         ` Philipp Gesang
2010-11-18 21:20     ` Aditya Mahajan
2010-11-18 22:12       ` Wolfgang Schuster
2010-11-19  1:05         ` Aditya Mahajan
2010-11-19 17:35           ` Wolfgang Schuster [this message]
2010-11-19 17:56             ` \definenamespace Hans Hagen
2010-11-19 18:05               ` \definenamespace Aditya Mahajan
2010-11-19 18:45                 ` \definenamespace Hans Hagen
2010-11-19 18:48               ` \definenamespace Wolfgang Schuster
2010-11-19 20:12                 ` \definenamespace Vianney le Clément
2010-11-19 20:31                   ` \definenamespace Hans Hagen
2010-11-19 17:11 ` The visual counter module Willi Egger

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=12CE99E6-0C02-4194-B352-4D42485AF13C@gmail.com \
    --to=schuster.wolfgang@googlemail.com \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).