q/337738/52406), and got the answer that
> what I want to do might not be possible.
>
> In my large document I have exercises (typeset with \startexercise
> \stopexercise, defined as an enumeration). Is it possible to use modes
> (or any other trick) to be able to compile the same file an
cument I have exercises (typeset with \startexercise
\stopexercise, defined as an enumeration). Is it possible to use modes
(or any other trick) to be able to compile the same file and get only
the exercises. For example,
context file.tex
should give the full document, while
context --mode=exe
as an enumeration). Is it possible to use modes
(or any other trick) to be able to compile the same file and get only
the exercises. For example,
context file.tex
should give the full document, while
context --mode=exercises file.tex
should give only all the exercises (or just everything "i
;, processfilemany },
}
}
Then, why is the product file processed multiple times?
because one might want to combine products (controlled by modes giving
different results) .. mostly downward compatible
-
time implies a \definemode for that mode. Doing so avoids
another macro to remember: less clutter for my brain ;-)
because one property of modes is that one doesn't have to define them,
you'd be quite unhappy if you would have to define all possible modes
that could be introduced in styles
The idea was
oids another macro to remember: less
clutter for my brain ;-)
because one property of modes is that one doesn't have to define them, you'd be
quite unhappy if you would have to define all possible modes that could be
introduced in styles
The idea was not to have the user define the mode, but
efined modes (that is, set with: \enablemode, \disablemode or
\definemode) can be tested about twice as fast as undefined modes which can
make a small difference
I do not understand this fully:
- if the mode is undefined, how can "define an undefined mode" for a mode that has
already be
> On 26 Jun 2014, at 12:08, Hans Hagen <pra...@wxs.nl> wrote:
>
> Another addition is that
>
> \definemode[something][keep]
>
> define an undefined mode; the keep makes sure that the already set value is
> kept (another option is 'yes').
>
&g
keys (see the documentation of filter
module[1], which is used by the vim module)
There are two modes: location=paragraph and location=text. In
location=paragraph you get
\blank[]
\blank[]
In location=text (which is used by \inline...) you get
The behaviour that you see is because
in both inline and display mode.
The output of \tfrac is wrong in both modes. In both modes, \tfrac should
equal the current output of \frac in inline mode.
Although I don't completely understand the code, my guess is that there is
a bug in how mathstyle=text is implemented (really, mathstyle
y a) ConTeXt and b) Lua?
Something like:
\mainlanguage[cz]
\ifmainlanguage{cz}
Do someting
\fi
and
if context.languages.active() == "cz" then
-- Do somthing
end
You can use the modes mechanism for this because you can use ** to
check for the main language (set by \mainlanguage)
active() == "cz" then
-- Do somthing
end
You can use the modes mechanism for this because you can use ** to
check for the main language (set by \mainlanguage) and * for the
current language (set by \language).
\mainlanguage[cs]
%\language[en]
\starttext
\doifelsemode{**cs}{The main l
s when writing the article on
modes. I'll update the wiki accordingly.
Aditya
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.
uested mode is enabled or disabled.
My bad. I thought that I had checked this when writing the article on
modes. I'll update the wiki accordingly.
Aditya___
If your question is of interest to others as well, plea
be included or not.
Is there a recommended design pattern that I could use for this type of
work?
I am not sure I completely understand your question, but have a look at
modes: http://wiki.contextgarden.net/Modes
Aditya
Perfect. I think that modes will work nicely.
To further explain my use case: I have a manuscript, which I would like
to continue to evolve with editorial comments, suggestions, ideas for
further development (some generated by the author, others by reviewers).
At any given time the text
Hello,
there are many modes for various situations
(http://wiki.contextgarden.net/Modes).
Is there a mode to signal being inside a footnote?
This would be handy for head definition:
\definehead[paragraph][subsubsubject]
\define\ShBlank{\doifnotmode{*footnote}{\blank}}
\setuphead
}{\placefootnotes}?
I discovered this (http://wiki.contextgarden.net/Modes#System_modes)
after the reply from Hans to my own question.
Ok, thanks Pablo; will explore this as well, especially after I start
writing the journal article.
Best wishes
Idris
--
Idris Samawi Hamid
Professor of Philosophy
in ConTeXt to setup \placefootnotes
etc. in a mode so that it gets invoked only in the export. Will explore
this for the article.]
How about the system mode: \doifmode{*export}{\placefootnotes}?
I discovered this (http://wiki.contextgarden.net/Modes#System_modes)
after the reply from Hans to my own
}{\placefootnotes}?
I discovered this (http://wiki.contextgarden.net/Modes#System_modes)
after the reply from Hans to my own question.
Ok, thanks Pablo; will explore this as well, especially after I start
writing the journal article.
Best wishes
Idris
--
Idris Samawi Hamid
Professor of Philosophy
}{
\dorecurse{10}{
\input zapf\par}}}
\stopmode
\stoptext
Output file sizes with different modes are the following:
--mode=repeated-image745KB
--mode=single-image 303KB
--mode=no-image 302KB
Although the image is the same (and it is only
\stoptext
Output file sizes with different modes are the following:
--mode=repeated-image745KB
--mode=single-image 303KB
--mode=no-image 302KB
Although the image is the same (and it is only embedded once) file size
with repeated image is almost two and a half times
with ImageMagick with two
directories (such as print-quality and screen-quality)?
If you use the same image file names, you could also use modes:
\enablemode[print]
\startmode[print]
\setupexternalfigures[location=/home/user/project/img-print/]
\stopmode
\startmode[screen
}}
\starttext
\es\mimo
\en\mimo
\stoptext
Headings except in PDF bookmarks are fine.
How can I get titles in PDF bookmarks?
You can’t use the \translate command to set different texts for bookmarks
because it is unexpandable.
What you can do is to use language dependent modes, e.g
modes, e.g.
Many thanks for your fast reply, Wolfgang.
This was exactly what I needed.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
If your question is of interest to others as well, please add
, but still “(van Halen 1984)” and “van Halen, Edward”. It
would be nice if you could switch between two modes while invoking the
citation. I have not yet discovered where this order is defined.
___
If your question
Wolfgang von” in the publications list, but
still “(van Halen 1984)” and “van Halen, Edward”. It would be nice if
you could switch between two modes while invoking the citation. I have
not yet discovered where this order is defined.
Greetings Jörg
would not have talked about “von Goethe” but
simply “Goethe”–so in a reference it would be “(Goethe 1774)” and “Goethe,
Johann Wolfgang von” in the publications list, but still “(van Halen 1984)”
and “van Halen, Edward”. It would be nice if you could switch between two
modes while invoking
.
For now I have an important question regarding in-text references:
Is there a way to switch between the following citation modes?
I have to manage:
* normal reference in brackets: author space year, no comma: e.g.
“(Einstein 1904)”
* author is named in the text, only year in brackets: e.g
.
Perhaps Modes ?
http://wiki.contextgarden.net/Modes
\starttext
\definebuffer[Slide]
foo
% \skipSlide
\startSlide
bla bla bla
\startyping
language C code
\stoptyping
bla bla bla
\stopSlide
bar
\stoptext
have students of different levels.
The gobbleinput solution is the best solution : I can activate or not a
slide according to my audience.
If I use the buffer solution, I'll not be able to deactivate the whole
slide containing the typing region.
Perhaps Modes ?
http://wiki.contextgarden.net
: I can activate or not a slide
according to my audience.
If I use the buffer solution, I'll not be able to deactivate the whole slide
containing the typing region.
Perhaps Modes ?
http://wiki.contextgarden.net/Modes
--
luigi
At least in MKIV. I haven't tried MKII.
The following example should demonstrate this. With no mode specified on
the command line, this should enable mode three and prevent and disable
the other modes. It seems that \preventmode is not only ineffective in
what it is described as doing
, is there a solution that could be keyed on
system modes or on section blocks, thus moving all of the styling to the
preamble (to use a LaTeX term)? I currently do that to support different
header formats in the body matter and appendices, using the following
method, but I suspect that there may be a more
\completecontent and
not \placelist[chapter,section], having excluded lower-level sectioning
headers via \setupcombinedlist. I am asking if there is a way to take
advantage of user-defined or system modes, or section blocks, to
accomplish this without requiring explicit markup (silentsection in your
example
matter parts and a different
depth for the appendices, is there a solution that could be keyed on
system modes or on section blocks, thus moving all of the styling to the
preamble (to use a LaTeX term)? I currently do that to support different
header formats in the body matter and appendices
the \startproduct).
The first problem is that it seems some of the functionality of
products, projects, and components is lost. But maybe that's a matter
of taste.
Another problem is that env.tex doesn't know that one is compiling a
product or component---thus, the system modes *product
(TeX-clean t) TeX-run-function nil t :help Delete
generated intermediate and output files) (Other TeX-run-command t
t :help Run an arbitrary command
'(TeX-default-mode (quote context-en-mode))
'(TeX-engine (quote luatex))
'(TeX-kpathsea-path-delimiter t)
'(TeX-modes (quote (tex-mode
a blank line, which doesn't stand out as
a syntax error in my mind, expecially when white space is supposed to be
ignored by tex/context in usual modes.
Has this been noticed before?
The below works successfully
\starttext
\placefigure
[here,none]
[fig: reference tag
] [file:Iwona-Regular.otf*withnodetwo]
\starttext
test 1, both modes:
{\iwonanone 0123456789abcdefghijklmnopqrstuvwxyz}\par
{\iwonabone 0123456789abcdefghijklmnopqrstuvwxyz}\par
{\iwonantwo 0123456789abcdefghijklmnopqrstuvwxyz}\par
{\iwonabtwo 0123456789abcdefghijklmnopqrstuvwxyz}\par
% test 2, base only
-Regular.otf*withnodeone]
\definefont [iwonabtwo] [file:Iwona-Regular.otf*withbasetwo]
\definefont [iwonantwo] [file:Iwona-Regular.otf*withnodetwo]
\starttext
test 1, both modes:
{\iwonanone 0123456789abcdefghijklmnopqrstuvwxyz}\par
{\iwonabone 0123456789abcdefghijklmnopqrstuvwxyz}\par
-Regular.otf*withnodeone]
\definefont [iwonabtwo] [file:Iwona-Regular.otf*withbasetwo]
\definefont [iwonantwo] [file:Iwona-Regular.otf*withnodetwo]
\starttext
test 1, both modes:
{\iwonanone 0123456789abcdefghijklmnopqrstuvwxyz}\par
{\iwonabone 0123456789abcdefghijklmnopqrstuvwxyz}\par
\setupsystem[\c!n=1,\c!m=1]
used options % modes
used options % options (not that important)
used options \startsetups *runtime:options
used options \stopsetups
used options % styles and modules
used options \startsetups *runtime:modules
used options \stopsetups
used
On 16/06/13 21:03, Wolfgang Schuster wrote:
Am 16.06.2013 um 09:46 schrieb Pablo Rodríguez oi...@web.de:
[...]
Is there no way to avoid orphans and widows in the lines
environment?
1. Don’t use * in your setups names because names starting with an
asterisk are system modes.
2. To load
names starting with an
asterisk are system modes.
2. To load the defaults settings you have to use \setups[*reset]
which needs the asterisks because it’s a system mode.
3.The settings doesn’t help because in the lines environment each
line is a separate paragraph which makes \widowpenalty
?
1. Don’t use * in your setups names because names starting with an
asterisk are system modes.
2. To load the defaults settings you have to use \setups[*reset]
which needs the asterisks because it’s a system mode.
3.The settings doesn’t help because in the lines environment each
line is a separate
\brokenpenalty=1
\stopsetups
I'm afraid that I get widow lines in the lines environment.
Is there no way to avoid orphans and widows in the lines environment?
1. Don’t use * in your setups names because names starting with an asterisk are
system modes.
2. To load the defaults
environment file
first (document styles)
mtx-context | --mode=listenable given the modes
(conditional processing in styles)
mtx-context | --path=listalso consult the given paths
when files are looked for
mtx-context | --arguments=list set variables that can
interface that
doesn't use predefined modes, but lets you setup the decimal mark,
separator mark, the input decimal mark, etc. Something like this:
\setupdigits
[inputdecimal={.}, % input 3.1415926535
decimal={,}
separator=\space,
groupsize=4, % output 3,1415 9265 45
, % or times=\cdot
]
+1
P.s: I've been thinking I'd like to write more contexty interface that
doesn't use predefined modes, but lets you setup the decimal mark,
separator mark, the input decimal mark, etc. Something like this:
\setupdigits
[inputdecimal={.}, % input
={,}, % --\setdigitorder{0}
signspace=yes,% --\setdigitsign{1}; '+ 1.4', not '+1.4'
times=\times, % or times=\cdot
]
Cheers,
Sietse
---
P.s: I've been thinking I'd like to write more contexty interface that
doesn't use predefined modes, but lets you setup the decimal
modes, but lets you setup the decimal mark,
separator mark, the input decimal mark, etc. Something like this:
\setupdigits
[inputdecimal={.}, % input 3.1415926535
decimal={,}
separator=\space,
groupsize=4, % output 3,1415 9265 45
signspace=,] % +3.14159
}
of use modes (often more natural)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma
parameter?
\getdocumentargument{myargument}
My first try did not work, but now it does. Properly made a silly
mistake somewhere.
of use modes (often more natural)
In this case it is not something to use, but it is certainly something
to look into.
--
Cecil Westerhof
(no error) if I
hard-code in 13pt instead of using an intervening \largefontsize
definition. But if I hard-code the point size, it would hamper the
modularity of our font configuration and the use of modes in which
different size fonts are used.
Maybe \define is just the wrong command to use when
\SerifL{Hello} \stoptext
Note that the SerifL font definition works fine (no error) if I
hard-code in 13pt instead of using an intervening \largefontsize
definition. But if I hard-code the point size, it would hamper the
modularity of our font configuration and the use of modes in which
Hello ConTeXist.
I would like use modes alternative to change of image dimensions in
different documents (presentation or print version).
Compilation in ConTeXt TeXLive 2012 version will compile without error,
but without visual effect. Compilation with the standalone version
fails. What
Am 05.02.2013 um 13:50 schrieb Jaroslav Hajtmar hajt...@gyza.cz:
Hello ConTeXist.
I would like use modes alternative to change of image dimensions in different
documents (presentation or print version).
Compilation in ConTeXt TeXLive 2012 version will compile without error, but
without
Thanx Wolfgang.
I might have guessed :-).
Anyway, thanks for inspiring solutions ...
Jaroslav Hajtmar
Dne 5.2.2013 14:15, Wolfgang Schuster napsal(a):
Am 05.02.2013 um 13:50 schrieb Jaroslav Hajtmar hajt...@gyza.cz:
Hello ConTeXist.
I would like use modes alternative to change of image
-use components. Other aspects are
- different modes (presentation, handout, manuscript)
- poster production
- nice graphics/animation via pstricks or metapost
- export to other formats (when writing articles many journals in my
field do not accept .tex-files)
- export to epub/mobi format. I
background.
Sure, I am using MacTeX and TeXLive now for many years.
What attracted me to ConTeXt was the project-product-component
structure to use and re-use components. Other aspects are
- different modes (presentation, handout, manuscript)
- poster production
- nice graphics
-component
structure to use and re-use components. Other aspects are
- different modes (presentation, handout, manuscript)
'modes' have always been around
- poster production
A1 papersizes are supported as are layers (the way to make posters).
- nice graphics/animation via pstricks
][name:GentiumBookBasic at \XXLfontsize]
\definefont[SerifXXLB][name:GentiumBookBasic-Bold at \XXLfontsize]
E16settings.tex: I added these definitions:
\define\XLfontsize{14pt}
\define\XXLfontsize{16pt}
There are modes involved, so things are a bit more complicated, but I
believe that is the only effective difference
]
\definefont[SerifXXL][name:GentiumBookBasic at \XXLfontsize]
\definefont[SerifXXLB][name:GentiumBookBasic-Bold at \XXLfontsize]
E16settings.tex: I added these definitions:
\define\XLfontsize{14pt}
\define\XXLfontsize{16pt}
There are modes involved, so things are a bit more complicated, but I
believe
}
//
// There are modes involved, so things are a bit more complicated, but I
// believe that is the only effective difference.
/
and how about:
\def\XLfontsize{14pt}
\def\XXLfontsize{16pt}
I will try that, but all our font size definitions have always used
\define, and it used to work fine without
.
/
// E16settings.tex: I added these definitions:
// \define\XLfontsize{14pt}
// \define\XXLfontsize{16pt}
//
// There are modes involved, so things are a bit more complicated, but I
// believe that is the only effective difference.
/
and how about:
\def\XLfontsize{14pt}
\def\XXLfontsize{16pt
takes the name of the current file as argument, the name
of
the file is tired in the command \currentcomponent. In MkIV you can replace the
name
with “*” and context would still print the correct name with \currentcomponent.
The asterisk in modes indicates that you use a system mode which
On 2012-09-10 Ian Lawrence physics.roo...@gmail.com wrote:
Hi Ian,
I'd like to pass variables into context on invocation, just as you can do
with setting modes
So
context --arguments=number=8, time=full-time --mode=trial test.tex
context --number=8 --time=full-time test.tex
the sequences like \v!and \c! etc. mean.
Are they references to modes?
--
John Culleton
Free list of books for self-publishers:
http://wexfordpress.net/shortlist.html
Police Procedural and Expose: Death Wore Black
Create Book Covers with Scribus
http://www.booklocker.com/books/4055.html
!before=,\c!after=]
I have no idea what the sequences like \v!and \c! etc. mean.
Are they references to modes?
Search for multi-lingual on this page:
http://wiki.contextgarden.net/System_Macros/Key_Value_Assignments
Aditya
I have no idea what the sequences like \v!and \c! etc. mean.
Are they references to modes?
I asked much the same question on tex.stackexchange.com two months
ago, except mine was not so nice and focused.
Aditya gave a very nice explanation of what the letters do; clearer
than the one
On 22-8-2012 23:02, Sietse Brouwer wrote:
I have no idea what the sequences like \v!and \c! etc. mean.
Are they references to modes?
I asked much the same question on tex.stackexchange.com two months
ago, except mine was not so nice and focused.
Aditya gave a very nice explanation of what
version will need to be double spaced. Obviously, I'd rather use the
existing source to generate both draft and well-formatted versions, so
it sounds like a job for modes. Before I start hacking, has someone
done this already or is ther an alternative method of accomplishing this?
Thanks,
Roger
ran context with --arrange
Sorry, I saw the thread modes + arranging by Thomas A. Schmitz just
as I pressed send.
I guess the next beta will fix it, yes?
Greetlings, Hraban
___
If your question is of interest
ran context with --arrange
Sorry, I saw Thomas’ thread modes + arranging only after pressing
send.
This is fixed with tonight’s beta, thank you!
But the table of content is missing now...
Greetlings, Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https
Hi all,
sorry for the slightly silly example, but it's something I can't figure
out, and it has worked before. For processing my documents, I have
defined a mode which will arrange pages. Here's the silly example test.tex:
\startmode[arranged]
\setuppapersize[A6][A4]
\setuparranging[2*4]
On 8-7-2012 20:06, Thomas A. Schmitz wrote:
Hi all,
sorry for the slightly silly example, but it's something I can't figure
out, and it has worked before. For processing my documents, I have
defined a mode which will arrange pages. Here's the silly example test.tex:
Can you test with
On 07/09/2012 12:17 AM, Hans Hagen wrote:
Can you test with
c_flags.noarrange = nil
in line 671 in mtx-context.lua (some time ago the 'opt' file has been
replaced by passing commandline arguments and this slipped through).
Hans
Hi Hans,
yes, when I change this line,
Hello,
this doesn't work for me:
\definestartstop[amode][before={\startmode[a]},
after={\stopmode}]
\starttext
All modes.
\startamode
``A'' mode.
\stopamode
\stoptext
Can I use \startmode with \definestartstop? Or is there a better way
to do something like
On 2012-06-26, at 10:12 PM, Marcin Borkowski mb...@wmi.amu.edu.pl wrote:
Hello,
this doesn't work for me:
\definestartstop[amode][before={\startmode[a]},
after={\stopmode}]
\starttext
All modes.
\startamode
``A'' mode.
\stopamode
\stoptext
Can I use
Am 26.06.2012 um 22:12 schrieb Marcin Borkowski:
Hello,
this doesn't work for me:
\definestartstop[amode][before={\startmode[a]},
after={\stopmode}]
\starttext
All modes.
\startamode
``A'' mode.
\stopamode
\stoptext
Can I use \startmode
}]
\starttext
All modes.
\startamode
``A'' mode.
\stopamode
\stoptext
Can I use \startmode with \definestartstop?
No you can’t.
I was afraid of this...
Or is there a better way to do something like this?
It depends on what you want to do. You can create a buffer command
modes.
\startamode
“A” mode.
\stopamode
\stoptext
Thanks, it worked. One question: is there any difference between
\def\starta{...}
\def\stopa{...}
and
\definestartstop[a][before={...},after={…}]
Yes because in my definition for \startamode I start a buffer which reads
\setupsystem[\c!n=2,\c!m=2]
used options % modes
used options % options (not that important)
used options \startsetups *runtime:options
used options \stopsetups
used options % styles and modules
used options \startsetups *runtime:modules
used options \stopsetups
used
options }
system options \stopluacode
system options % process info
system options \setupsystem[inputfile=kk.tex]
system options \setupsystem[\c!n=1,\c!m=1]
system options % modes
system options % options (not that important
used options % process info
used options \setupsystem[inputfile=g]
used options \setupsystem[\c!n=3,\c!m=1]
used options \enabledirectives[system.runonce]
used options % modes
used options % options (not that important)
used options \startsetups *runtime:options
used
document.files={
used options linewrap,
used options }
used options \stopluacode
used options % process info
used options \setupsystem[inputfile=linewrap]
used options \setupsystem[\c!n=2,\c!m=2]
used options % modes
used options % options (not that important)
used
options document.files={
used options code,
used options }
used options \stopluacode
used options % process info
used options \setupsystem[inputfile=code]
used options \setupsystem[\c!n=2,\c!m=2]
used options % modes
used options % options (not that important)
used
document.arguments={
used options }
used options document.files={
used options linewrap,
used options }
used options \stopluacode
used options % process info
used options \setupsystem[inputfile=linewrap]
used options \setupsystem[\c!n=2,\c!m=2]
used options % modes
used options
line driven)
\unprotect
% feedback and basic job control
% handy for special styles
\startluacode
document = document or { }
document.arguments={
}
document.files={
2,
}
\stopluacode
% process info
\setupsystem[inputfile=2]
\setupsystem[\c!n=1,\c!m=1]
% modes
% options (not that important
to use with modes - but the answer must be an other.
No, I get the result you want with my code.
\startmode[booklet]
\setuppapersize[A5][A4,landscape]
\setuparranging[2SIDE]
\stopmode
\starttext
One
\page
\startmode[booklet]
\null \page
\stopmode
Two
\page
Three
\page
Four
\page
Five
the
desired empty page manually.
On a wild guess: if you want different versions for print and for
screen, you can use modes (that's what I do for some of my stuff). in
pseudo-code:
\startmode[booklet]
\setuppapersize[A5][A4,landscape]
\setuparranging[2SIDE]
\stopmode
\starttext
First page
With your code I get:
1 2 first page of the pdf
3 4 second
5 6 third
7 8 fourth
But I want to get:
1 first page of the pdf (coverpage)
2 3 second
4 5 third
6 7 fourth
8 fifth (coverpage)
I know how to use with modes - but the answer must
with modes - but the answer must be an other.
Maybe I have to explain it more clearly:
on the first PDF-Page (A5) there should be only the cover-page (page 1)
\setuppapersize[A5][A5]
\setuparranging[1SIDE]%- I don't know how to write it - nothing was
working
On the second PDF-Page
\stopluacode
used options % process info
used options \setupsystem[inputfile=Source/Makeup/Table_of_Contents_Standalone_Product.tex]
used options \setupsystem[\c!n=1,\c!m=1]
used options % modes
used options % options (not that important)
used options \startsetups *runtime:options
=Source/Makeup/Table_of_Contents_Standalone_Product.tex]
used options \setupsystem[\c!n=1,\c!m=1]
used options % modes
used options % options (not that important)
used options \startsetups *runtime:options
used options \stopsetups
used options % styles and modules
used options
% process info
used options \setupsystem[inputfile=Source/Handbook.tex]
used options \setupsystem[file=Avaneya Project Crew Handbook.pdf]
used options \setupsystem[\c!n=1,\c!m=1]
used options % modes
used options % options (not that important)
used options \startsetups
[inputfile=test_crossref1.tex]
system options \setupsystem[\c!n=1,\c!m=1]
system options % modes
system options % options (not that important)
system options \startsetups *runtime:options
system options \setuparranging[\v!disable]
system
options \setupsystem[inputfile=K2.tex]
used options \setupsystem[\c!n=1,\c!m=1]
used options % modes
used options % options (not that important)
used options \startsetups *runtime:options
used options \stopsetups
used options % styles and modules
used options
}
used options \stopluacode
used options % process info
used options \setupsystem[inputfile=K2.tex]
used options \setupsystem[\c!n=1,\c!m=1]
used options % modes
used options % options (not that important)
used options \startsetups *runtime:options
used options
201 - 300 of 647 matches
Mail list logo
