Hi, (1) --mode=modelist (1.1) Is there a limit to the number of modes in modelist ? (1.2) Is there a way to call the modelist and submit it to conditional testing within ConTeXt ? For example, to lookup (true/false) the presence of modes containing/starting with (an) alphannumeric string(s) ? (2) --modefile=file (2.1) What's the syntax of a modefile ? (2.2) How does ConTeXt handle a modefile ? Are the modes parsed into a modelist ( re: question 1.2 ) ? -- Best, Alan * using ConTeXt ver: 2008.08.18 14:00 MKIV fmt: 2008.8.22 int: english/english (on Windows XP)
Alan Stone wrote:
Hi,
(1) --mode=modelist
(1.1) Is there a limit to the number of modes in modelist ?
no, just what the console and memory permit
(1.2) Is there a way to call the modelist and submit it to conditional testing within ConTeXt ? For example, to lookup (true/false) the presence of modes containing/starting with (an) alphannumeric string(s) ?
\doifmodeelse{somemode} { } { } etc etc etc
(2) --modefile=file
(2.1) What's the syntax of a modefile ?
this concerns examodes stuff that we use for process control at pragma
(2.2) How does ConTeXt handle a modefile ? Are the modes parsed into a modelist ( re: question 1.2 ) ?
best use ctx files instead, like in == somefile.ctx === <?xml version='1.0' standalone='yes'?> ctx:job ctx:preprocess/ ctx:flags ctx:flagtexengine=luatex ctx:flaginterface=en ctx:process ctx:resources ctx:modeproofing ctx:environmentsomestyle.tex ctx:postprocess/ texexec .... --ctx=somefile ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Hans Hagen wrote:
(1.2) Is there a way to call the modelist and submit it to conditional testing within ConTeXt ? For example, to lookup (true/false) the presence of modes containing/starting with (an) alphannumeric string(s) ?
\doifmodeelse{somemode} { } { } etc etc etc
This presumes that you actually know the list of enabled modes, so I think a commalist of "set modes" would be useful as well. Modules could use that to set up keyword-based behaviours. Best wishes, Taco
Taco Hoekwater wrote:
Hans Hagen wrote:
(1.2) Is there a way to call the modelist and submit it to conditional testing within ConTeXt ? For example, to lookup (true/false) the presence of modes containing/starting with (an) alphannumeric
\doifinstring
string(s) ? \doifmodeelse{somemode} { } { } etc etc etc
This presumes that you actually know the list of enabled modes, so I think a commalist of "set modes" would be useful as well. Modules could use that to set up keyword-based behaviours.
there is already such a mechanism (thomas uses it in his module) maybe at some point in mkiv we can provide the list because then i can use lua for keeping track of things; maintaining a comma separated list is tex is not that fast (and i use modes a lot to control styles that need a high performance); think of \enablemode[a,b,c] and a large list of enabled modes that we need to check for already set nodes (in lua it's just a hash and a the fill list a list-of-keys) btw, this would make mkiv incompatible with mkii ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On Thu, Sep 11, 2008 at 1:37 PM, Hans Hagen
Taco Hoekwater wrote:
Hans Hagen wrote:
(1.2) Is there a way to call the modelist and submit it to conditional testing within ConTeXt ? For example, to lookup (true/false) the presence of modes containing/starting with (an) alphannumeric
\doifinstring
string(s) ? \doifmodeelse{somemode} { } { } etc etc etc
This presumes that you actually know the list of enabled modes, so I think a commalist of "set modes" would be useful as well. Modules could use that to set up keyword-based behaviours.
there is already such a mechanism (thomas uses it in his module)
Is this mechanism documented somewhere ?
maybe at some point in mkiv we can provide the list because then i can use lua for keeping track of things; maintaining a comma separated list is tex is not that fast (and i use modes a lot to control styles that need a high performance); think of
\enablemode[a,b,c]
and a large list of enabled modes that we need to check for already set nodes (in lua it's just a hash and a the fill list a list-of-keys)
btw, this would make mkiv incompatible with mkii
-- Best, Alan * using ConTeXt ver: 2008.08.18 14:00 MKIV fmt: 2008.8.22 int: english/english (on Windows XP)
On Thu, Sep 11, 2008 at 12:52 PM, Taco Hoekwater
Hans Hagen wrote:
(1.2) Is there a way to call the modelist and submit it to conditional testing within ConTeXt ? For example, to lookup (true/false) the presence of modes containing/starting with (an) alphannumeric string(s) ?
\doifmodeelse{somemode} { } { } etc etc etc
This presumes that you actually know the list of enabled modes, so I think a commalist of "set modes" would be useful as well. Modules could use that to set up keyword-based behaviours.
That's what I meant. Thanks for clarifying.
Best wishes, Taco
-- Best, Alan * using ConTeXt ver: 2008.08.18 14:00 MKIV fmt: 2008.8.22 int: english/english (on Windows XP)
On Thu, Sep 11, 2008 at 12:46 PM, Hans Hagen
Alan Stone wrote:
Hi,
(1) --mode=modelist
(1.1) Is there a limit to the number of modes in modelist ?
no, just what the console and memory permit
(1.2) Is there a way to call the modelist and submit it to conditional testing within ConTeXt ? For example, to lookup (true/false) the presence of modes containing/starting with (an) alphannumeric string(s) ?
\doifmodeelse{somemode} { } { } etc etc etc
(2) --modefile=file
(2.1) What's the syntax of a modefile ?
this concerns examodes stuff that we use for process control at pragma
(2.2) How does ConTeXt handle a modefile ? Are the modes parsed into a modelist ( re: question 1.2 ) ?
best use ctx files instead, like in
== somefile.ctx ===
<?xml version='1.0' standalone='yes'?>
ctx:job ctx:preprocess/ ctx:flags ctx:flagtexengine=luatex ctx:flaginterface=en ctx:process ctx:resources ctx:modeproofing ctx:environmentsomestyle.tex ctx:postprocess/
texexec .... --ctx=somefile
As I'm not familiar with XML, neither using ConTeXt with XML... What if I want to pass a list of modes: mode1, mode2, mode3, .... ? -- Best, Alan * ConTeXt ver: 2008.09.10 14:01 MKIV fmt: 2008.9.14 int: english/english * Windows XP Home SP3
Alan Stone wrote:
On Thu, Sep 11, 2008 at 12:46 PM, Hans Hagen
wrote: Alan Stone wrote:
Hi,
(1) --mode=modelist
(1.1) Is there a limit to the number of modes in modelist ? no, just what the console and memory permit
(1.2) Is there a way to call the modelist and submit it to conditional testing within ConTeXt ? For example, to lookup (true/false) the presence of modes containing/starting with (an) alphannumeric string(s) ? \doifmodeelse{somemode} { } { } etc etc etc
(2) --modefile=file
(2.1) What's the syntax of a modefile ? this concerns examodes stuff that we use for process control at pragma
(2.2) How does ConTeXt handle a modefile ? Are the modes parsed into a modelist ( re: question 1.2 ) ? best use ctx files instead, like in
== somefile.ctx ===
<?xml version='1.0' standalone='yes'?>
ctx:job ctx:preprocess/ ctx:flags ctx:flagtexengine=luatex ctx:flaginterface=en ctx:process ctx:resources ctx:modeproofing ctx:environmentsomestyle.tex ctx:postprocess/
texexec .... --ctx=somefile
As I'm not familiar with XML, neither using ConTeXt with XML...
What if I want to pass a list of modes: mode1, mode2, mode3, .... ?
just add more ctx:modeanothermode ctx:modeandanotherone ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Are such macros possible ? modes: ma, mb, ... mz values: va, vb, ... vz command: cmd parameter: p (1) instead of \doifmode{ma}{\cmd[name][va]} \doifmode{mb}{\cmd[name][vb]} ... \doifmode{mz}{\cmd[name][vz]} a macro which does: \doifmode{m*}{\cmd[name][v*]} (2) instead of \doifmode{ma}{\cmd[p=va]} \doifmode{mb}{\cmd[p=vb]} ... \doifmode{mz}{\cmd[p=vz]} a macro which does: \doifmode{m*}{\cmd[p=v*]} -- Best, Alan * texmfstart texexec --lua foo * ConTeXt ver: 2008.09.16 19:49 MKIV fmt: 2008.9.20 int: english/english * Windows XP Home SP3
Alan Stone wrote:
Are such macros possible ?
modes: ma, mb, ... mz values: va, vb, ... vz command: cmd parameter: p
(1) instead of
\doifmode{ma}{\cmd[name][va]} \doifmode{mb}{\cmd[name][vb]} .... \doifmode{mz}{\cmd[name][vz]}
a macro which does: \doifmode{m*}{\cmd[name][v*]}
(2) instead of
\doifmode{ma}{\cmd[p=va]} \doifmode{mb}{\cmd[p=vb]} .... \doifmode{mz}{\cmd[p=vz]}
a macro which does: \doifmode{m*}{\cmd[p=v*]}
nl, because there is no knowledge of what modes are set (i could cook something up for mkiv or course) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On Sat, Sep 20, 2008 at 6:07 PM, Hans Hagen
Alan Stone wrote:
Are such macros possible ?
modes: ma, mb, ... mz values: va, vb, ... vz command: cmd parameter: p
(1) instead of
\doifmode{ma}{\cmd[name][va]} \doifmode{mb}{\cmd[name][vb]} .... \doifmode{mz}{\cmd[name][vz]}
a macro which does: \doifmode{m*}{\cmd[name][v*]}
(2) instead of
\doifmode{ma}{\cmd[p=va]} \doifmode{mb}{\cmd[p=vb]} .... \doifmode{mz}{\cmd[p=vz]}
a macro which does: \doifmode{m*}{\cmd[p=v*]}
nl, because there is no knowledge of what modes are set (i could cook something up for mkiv or course)
Is there something like, or the equivalent of, one/two dimensional arrays in (Con)TeXt ? array1={ma, mb, ... mz} array2={va, vb, ... vz} or array{{ma,va}, {mb,vb} ... {mz,vz}} -- Best, Alan * texmfstart texexec --lua foo * ConTeXt ver: 2008.09.16 19:49 MKIV fmt: 2008.9.20 int: english/english * Windows XP Home SP3
Alan Stone wrote:
On Sat, Sep 20, 2008 at 6:07 PM, Hans Hagen
wrote: Alan Stone wrote:
Are such macros possible ?
modes: ma, mb, ... mz values: va, vb, ... vz command: cmd parameter: p
(1) instead of
\doifmode{ma}{\cmd[name][va]} \doifmode{mb}{\cmd[name][vb]} .... \doifmode{mz}{\cmd[name][vz]}
a macro which does: \doifmode{m*}{\cmd[name][v*]}
(2) instead of
\doifmode{ma}{\cmd[p=va]} \doifmode{mb}{\cmd[p=vb]} .... \doifmode{mz}{\cmd[p=vz]}
a macro which does: \doifmode{m*}{\cmd[p=v*]} nl, because there is no knowledge of what modes are set (i could cook something up for mkiv or course)
Is there something like, or the equivalent of, one/two dimensional arrays in (Con)TeXt ?
array1={ma, mb, ... mz} array2={va, vb, ... vz}
comma separated lists are used at several spots but usage really depends on the problem to be solved ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On Thu, Sep 11, 2008 at 12:46 PM, Hans Hagen
Alan Stone wrote:
(2.2) How does ConTeXt handle a modefile ? Are the modes parsed into a modelist ( re: question 1.2 ) ?
best use ctx files instead, like in
== somefile.ctx ===
<?xml version='1.0' standalone='yes'?>
ctx:job ctx:preprocess/ ctx:flags ctx:flagtexengine=luatex ctx:flaginterface=en ctx:process ctx:resources ctx:modeproofing ctx:environmentsomestyle.tex ctx:postprocess/
texexec .... --ctx=somefile
How about the other texexec options, re: http://linux.die.net/man/1/texexec ? Which ones go where in the ctx file + what is their syntax ? -- Best, Alan Ubuntu 8.04 Hardy Heron (Desktop) * ConTeXt ver: 2008.09.16 19:49 MKIV fmt: 2008.9.20 int: english/english (ConTeXt minimals installation) * texexec --lua foo
Alan Stone wrote:
On Thu, Sep 11, 2008 at 12:46 PM, Hans Hagen
wrote: Alan Stone wrote:
(2.2) How does ConTeXt handle a modefile ? Are the modes parsed into a modelist ( re: question 1.2 ) ? best use ctx files instead, like in
== somefile.ctx ===
<?xml version='1.0' standalone='yes'?>
ctx:job ctx:preprocess/ ctx:flags ctx:flagtexengine=luatex ctx:flaginterface=en ctx:process ctx:resources ctx:modeproofing ctx:environmentsomestyle.tex ctx:postprocess/
texexec .... --ctx=somefile
How about the other texexec options,
i implement them stepwise, i leave out those no longer relevant and all --pdf* ones will be done with ctx files instead ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On Mon, Sep 29, 2008 at 10:37 PM, Hans Hagen
Alan Stone wrote:
On Thu, Sep 11, 2008 at 12:46 PM, Hans Hagen
wrote: Alan Stone wrote:
(2.2) How does ConTeXt handle a modefile ? Are the modes parsed into a modelist ( re: question 1.2 ) ? best use ctx files instead, like in
== somefile.ctx ===
<?xml version='1.0' standalone='yes'?>
ctx:job ctx:preprocess/ ctx:flags ctx:flagtexengine=luatex ctx:flaginterface=en ctx:process ctx:resources ctx:modeproofing ctx:environmentsomestyle.tex ctx:postprocess/
texexec .... --ctx=somefile
How about the other texexec options,
i implement them stepwise, i leave out those no longer relevant and all --pdf* ones will be done with ctx files instead
Are there currently other ones than those listed above which already have been implemented ? How can one follow along which additional ones are implemented with the update releases ? -- Best, Alan Ubuntu 8.04 Hardy Heron (Desktop) * ConTeXt ver: 2008.09.16 19:49 MKIV fmt: 2008.9.20 int: english/english (ConTeXt minimals installation) * texexec --lua foo
Alan Stone wrote:
Are there currently other ones than those listed above which already have been implemented ?
How can one follow along which additional ones are implemented with the update releases ?
--help or just looking at the code i have no time to write/update a manual now Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (3)
-
Alan Stone
-
Hans Hagen
-
Taco Hoekwater