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]}
>
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
Alan Stone wrote:
> On Thu, Sep 11, 2008 at 12:46 PM, Hans Hagen <[EMAIL PROTECTED]> wrote:
>
>> Alan Stone wrote:
>>> Hi,
>>>
>>> (1) --mode=modelist
>>>
>>> (1.1) Is there a limit to the number of modes in modelist ?
>> no, j
On Thu, Sep 11, 2008 at 12:46 PM, Hans Hagen <[EMAIL PROTECTED]> 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
>
&
On Thu, Sep 11, 2008 at 1:37 PM, Hans Hagen <[EMAIL PROTECTED]> wrote:
> 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
On Thu, Sep 11, 2008 at 12:52 PM, Taco Hoekwater <[EMAIL PROTECTED]> 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
>>> pres
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) alphannumeri
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{so
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,
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
Never mind, the main sections system modes do the trick.
Best,
Alan
On Fri, Aug 1, 2008 at 11:42 AM, Alan Stone
<[EMAIL PROTECTED]>wrote:
> Unless I'm mistaken, the non-documented *headertext isn't operational any
> more.
> Has it been replaced with something else ? If
t; Hi,
> >
> > There are *some* system modes listed in the modes manual and main manual.
> > Are *all* system modes listed somewhere ?
>
> only the official ones -)
>
> when you uncover features in the manual that is not documented it can be
>
> - something new,
Alan Stone wrote:
> Hi,
>
> There are *some* system modes listed in the modes manual and main manual.
> Are *all* system modes listed somewhere ?
The modes manual has all modes documented except for a really obscure
one (as Hans explained). There is a small error, though: "*ma
Alan Stone wrote:
> Hi,
>
> There are *some* system modes listed in the modes manual and main manual.
> Are *all* system modes listed somewhere ?
only the official ones -)
when you uncover features in the manual that is not documented it can be
- something new, official, th
Hi,
There are *some* system modes listed in the modes manual and main manual.
Are *all* system modes listed somewhere ?
Alan
___
If your question is of interest to others as well, please add an entry to the
Wiki
"private". People who are in the private
> group should see everything, the group internal only the public parts
> and the internal ones. As far as I see, modes are not additive.
> What would be the best way to structure such a document and to style
> the different pa
the private
group should see everything, the group internal only the public parts
and the internal ones. As far as I see, modes are not additive.
What would be the best way to structure such a document and to style
the different paragraphs, so that the different audiences see, who can
read what
Hans van der Meer wrote:
> I guess the pairing of \startnotallmodes with \stopnotallmodes is at
> fault.
> In core-var.tex 234-235 I see:
> \long\def\dostartnotallmodes[#1]%
>{\docheckforallmodes\dostopallmodes\donothing{#1}}
> should be:
> \long\def\dostartnotallmodes[#1]%
>{\docheckfor
The following works mirabile dictu:
\enablemode[b,c]
\startallmodes[b,c]
\type{\startallmodes[b,c]} done
\stopallmodes
\startnotallmodes[c]
\type{\startallmodes[b,c]} not done
\stopallmodes %
But the following gives an error:
\enablemode[b,c]
\st
Taco Hoekwater wrote:
> David Arnold wrote:
>
>> All,
>>
>> Is this sort of thing ok?
>>
>> texexec --mode=short,copyright,paging chapter1
>>
>
> I think so ...
>
ah, i see, the chapter 1 is not part of the mode
David Arnold wrote:
> All,
>
> Is this sort of thing ok?
>
> texexec --mode="short,copyright,paging chapter1"
>
texexec --mode="short,copyright,paging chapter1"
...
\doifmodeelse{short,pagine chapter 1}
should work
-
David Arnold wrote:
> All,
>
> Is this sort of thing ok?
>
> texexec --mode=short,copyright,paging chapter1
I think so ...
Taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
All,
Is this sort of thing ok?
texexec --mode=short,copyright,paging chapter1
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
xexec.flag.pdfopen) $(1)
> Hans Hagen <[EMAIL PROTECTED]> wrote:
>
>> [EMAIL PROTECTED] wrote:
>>
>>> All,
>>>
>>> I am using the Scite editor provided by one of the Context dristributions.
>>>
>>> Is there a way to
vided by one of the Context dristributions.
> >
> > Is there a way to include modes with one of the various compiling commands?
> >
> no, but you can
>
> (1) temporary put \enablemode[...] at the to of the file
> (2) use a separate
[EMAIL PROTECTED] wrote:
> All,
>
> I am using the Scite editor provided by one of the Context dristributions.
>
> Is there a way to include modes with one of the various compiling commands?
>
btw, you can make a local scite options file and add menu items (key bindings);
[EMAIL PROTECTED] wrote:
> All,
>
> I am using the Scite editor provided by one of the Context dristributions.
>
> Is there a way to include modes with one of the various compiling commands?
>
no, but you can
(1) temporary put \enablemode[...] at the to of the file
(2) u
All,
I am using the Scite editor provided by one of the Context dristributions.
Is there a way to include modes with one of the various compiling commands?
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Johan Sandblom wrote:
Hello.
Doing
texmfstart texexec
now appears to call newtexexec. However, newtexexec does not seem to
handle --mode at all. Is it coming? Should I set it up so I can call
texexec directly in order to use modes?
i ran into that as well, it does recognize the modes
Hello.
Doing
texmfstart texexec
now appears to call newtexexec. However, newtexexec does not seem to
handle --mode at all. Is it coming? Should I set it up so I can call
texexec directly in order to use modes?
Regards, Johan
--
Johan Sandblom N8, MRC, Karolinska sjh
t +46851776108 17176
Well, I am very glad that you said something. I was feeling unusually
sheepish for having missed it!
Cheers, Alan
On Oct 17, 2005, at 4:45 PM, Henning Hraban Ramm wrote:
Am 2005-10-17 um 19:04 schrieb Alan Bowen:
Many thanks. That is helpful and much appreciated. I missed the
closing rem
Am 2005-10-17 um 19:04 schrieb Alan Bowen:
Many thanks. That is helpful and much appreciated. I missed the
closing remark about \enablemode on the Mode page of ConTeXt wiki
That's no wonder - I added it this morning after I read Willi's mail.
>;->>
Grüßlis vom Hraban!
---
http://www.fie
Many thanks, Hans. The idea of a pop-up menu for texexec does have a
peculiar charm.
Best, Alan
On Oct 17, 2005, at 4:21 AM, Hans Hagen wrote:
Alan Bowen wrote:
Following the example in the ConTeXt Wiki (http://
wiki.contextgarden.net/Modes) I have defined an environment file
that
to solve:
%\enablemode[screen]
\enablemode[print]
\envrionment yourenvironment
Important is to enable the required mode before loading the
environment file. - Dit you know that you can select multiple modes
e.g. you have a print-mode and the document should be created for
letter, A4 and A5. So
Alan Bowen wrote:
Following the example in the ConTeXt Wiki (http://
wiki.contextgarden.net/Modes) I have defined an environment file that
specifies two modes (screen, print) for the production of the same
source file. This works well when the appropriate texexec commands
are given at the
Hi Alan,
This is simle to solve:
%\enablemode[screen]
\enablemode[print]
\envrionment yourenvironment
Important is to enable the required mode before loading the environment
file. - Dit you know that you can select multiple modes e.g. you have a
print-mode and the document should be created
Following the example in the ConTeXt Wiki (http://
wiki.contextgarden.net/Modes) I have defined an environment file that
specifies two modes (screen, print) for the production of the same
source file. This works well when the appropriate texexec commands
are given at the command line.
The
Reminds me of this post:
http://archive.contextgarden.net/message/20041101.205339.1e76d98d.html
I bet that is what we all do!
David
Matthias Weber :
> Hello again,
>
> oh my, this was a stupid mistake. I added the
> [screen] and [print] parameters to \stopmode.
> No wonder that is what is being
possible to
give you a meaningful answer if there is no detailed information.
Could you provide a minimal example which is producing the mentioned
bahviour?
Willi
Matthias Weber wrote:
Hello,
when using modes, the names of all used modes are printed on the
first page
of the document like
[screen
Hello Willi,
I have just change a major projects to modes, so in producing a minimal
example
the effect takes a slightly different form:
\starttext
\disablemode[screen]
\enablemode[print]
\startmode[screen]
Screen Version
\stopmode[screen]
\startmode[print]
Print Version
\stopmode[print
Hi Matthias
I see there is a problem in your case. Still it is not possible to give
you a meaningful answer if there is no detailed information.
Could you provide a minimal example which is producing the mentioned
bahviour?
Willi
Matthias Weber wrote:
Hello,
when using modes, the names of all
Hello,
when using modes, the names of all used modes are printed on the first
page
of the document like
[screen]
[print]
etc.
What's the purpose, and how can I get rid of this?
I could see this being useful if the disabled modes were stricken out.
Thanks,
Mat
On Sat, 14 Jun 2003, Hans Hagen wrote:
> >* tables
> >- same as table, but can break over several pages
> >- [start|stop]table[head|tail] works
> >- nowhere documented?
>
> in my still to be included chapter if the manual it is -)
Hello,
I am looking for documentation for tables.
Is the table-cha
Hi,
The next version will have a new system mode, which can be used in
conditional processing:
\startmode[*first]
...
\stopmode
this mode is true in the first run and can be used like:
\startmode[*first]
\executesystemcommand{dowhatever test.tex x-test.tex}
\stopmode
\typefile{x-test.tex}
At 22:53 16/06/2003 +0200, you wrote:
Am Sonntag, 15.06.03, um 20:01 Uhr (Europe/Zurich) schrieb Hans Hagen:
\starttabulatehead
\NC left \NC right \NC \NR
\stoptabulatehead
It gives the following error
is this a matter of stach size or do others have the same problem?
I got the same (or somethin
Am Sonntag, 15.06.03, um 20:01 Uhr (Europe/Zurich) schrieb Hans Hagen:
\starttabulatehead
\NC left \NC right \NC \NR
\stoptabulatehead
It gives the following error
is this a matter of stach size or do others have the same problem?
I got the same (or something similar), and I run the latest beta,
At 00:22 15/06/2003 +0100, you wrote:
\starttabulatehead
\NC left \NC right \NC \NR
\stoptabulatehead
It gives the following error
This is pdfeTeX, Version 3.14159-1.10b-2.1 (Web2C 7.4.5) (format=cont-en
2003.4.28) 14 JUN 2003 19:16
...many lines cut...
! TeX capacity exceeded, sorry [input st
Hans,
This does not work for me either
\starttabulatehead
\NC left \NC right \NC \NR
\stoptabulatehead
It gives the following error
This is pdfeTeX, Version 3.14159-1.10b-2.1 (Web2C 7.4.5) (format=cont-en
2003.4.28) 14 JUN 2003 19:16
...many lines cut...
! TeX capacity exceeded, sorry [input
At 18:32 12/06/2003 +0200, you wrote:
Ahoi!
I just reviewed my german ConTeXt tutorial and tried to tell the truth
about all the table modes. Please correct me if I'm wrong:
* tabulate
- can break over several pages
- [start|stop]tabulate[head|tail] should define a repeated head/tail,
b
Ahoi!
I just reviewed my german ConTeXt tutorial and tried to tell the truth
about all the table modes. Please correct me if I'm wrong:
* tabulate
- can break over several pages
- [start|stop]tabulate[head|tail] should define a repeated head/tail,
but it doesn't work
- documented in
101 - 150 of 150 matches
Mail list logo
