Dear list,
Motivated by this question on TeX.SX
https://tex.stackexchange.com/questions/369778
I took a look at the \definenamespace mechanism in ConTeXt.
It seems that it permits a syntax like
\define[...,...][...=...,...=...]
where you can provide a list of instances to define in the first
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%
On 19-11-2010 6:35, Wolfgang Schuster wrote:
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:
On Fri, 19 Nov 2010, Hans Hagen wrote:
On 19-11-2010 6:35, Wolfgang Schuster wrote:
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
On 19-11-2010 7:05, Aditya Mahajan wrote:
\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
\ifthirdargument
\getparameters[#1#4][\s!parent=#1##2,##3]%
Am 19.11.2010 um 18:56 schrieb Hans Hagen:
or maybe:
\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
\ifthirdargument
Could there also be a bug in the \setup command definition:
\unexpanded\def\doinstallsetuphandler#1#2#3#4#5%
{\unexpanded\def#2{\dodoubleempty#4}%
\newtoks#5%
\def#4[##1][##2]%
{\ifsecondargument
\def\docommand1% we will have a simple one as well
{\edef#3{##1}%
On 19-11-2010 9:12, Vianney le Clément wrote:
{\edef#3{1}%-- argument of \docommand
indeed
PS: just to learn some TeXnical details, could someone explain what
the \unexpanded is supposed to do here?
it is etex's \protected prefix and not to be confused with the etex
On 2010-11-18 04:56:27, Wolfgang Schuster wrote:
Am 18.11.2010 um 01:36 schrieb Philipp Gesang:
Hi Wolfgang,
of course you are always welcome to deliver this kind of
thorough discussion! The wiki is grateful …
Just two keys remain unexplained: “version” and “comment”. I
guess
On Wed, 17 Nov 2010, Wolfgang Schuster wrote:
I’m not Aditya but i hope you will also accept my explanation.
This is a much better explanation than I could have written. Just a few
points:
I will start with the first argument and the „type“ key, e.g.
\definenamespace
[fancybreak]
On Thu, 18 Nov 2010, Wolfgang Schuster wrote:
\nameparameter use the value from \currentname while \namednameparameter
has two argument where the first argument is the name of a command or
environment
created with \definename. \detokenized... is important when you pass values
from tex to lua
Am 17.11.2010 um 20:10 schrieb Philipp Gesang:
Hi Aditya,
you seem to be familiar with some of the features of the new
namespace model that I was not able to infer from Wolfgang’s
code. Could you please comment on what the keys ‘setup’, ‘type’,
and ‘command’ in ‘\definenamespace’
On 2010-11-17 22:53:20, Wolfgang Schuster wrote:
Am 17.11.2010 um 20:10 schrieb Philipp Gesang:
Hi Aditya,
you seem to be familiar with some of the features of the new
namespace model that I was not able to infer from Wolfgang’s
code. Could you please comment on what the keys
Am 18.11.2010 um 01:36 schrieb Philipp Gesang:
Hi Wolfgang,
of course you are always welcome to deliver this kind of
thorough discussion! The wiki is grateful …
Just two keys remain unexplained: “version” and “comment”. I
guess they are not as critical but for sake of completeness and
Hi all!
On 2010-09-25 19:35:31, Wolfgang Schuster wrote:
Am 25.09.2010 um 17:07 schrieb Philipp Gesang:
Could you please explain what these other parameters do:
style=yes,
parent=fb
Also, what other values would the parameter ‘setup’ accept
besides ‘list’?
I’ll come back to
On 2010-09-23 23:43:15, Wolfgang Schuster wrote:
These are namespaces but you don't need these constructs
anymore in mkiv because there is now a \definenamespace command
which takes care of this.
Hi Wolfgang,
following your fancybreak module I put together dummy module.
Am 25.09.2010 um 17:07 schrieb Philipp Gesang:
Could you please explain what these other parameters do:
style=yes,
parent=fb
Also, what other values would the parameter ‘setup’ accept
besides ‘list’?
I’ll come back to this later.
BTW: The two letter namespaces are reserved for Hams and
17 matches
Mail list logo
