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]
\startallmodes[b,c]
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?
Thanks in advance,
__Janko
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
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
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
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
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
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
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]
Hi,
(for module writers)
The latest beta gives access to modes at the lua end
\starttext
\enablemode[test]
\enablemode[]
\doifallmodes{test,xxx}{NO}
\doifallmodes{test,}{YES}
\doifmode{test}{YES}
\doifnotmode{xxx}{YES}
\startluacode
tex.sprint(tex.modes['x']and YES or NOP
Am 2010-10-14 um 15:57 schrieb Hans Hagen:
(for module writers)
The latest beta gives access to modes at the lua end
Wikified (unmodified):
http://wiki.contextgarden.net/Modes#Modes_in_LuaTeX
Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http
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,
Matthias
Hello,
Here is a problem with nested modes:
\starttext
no mode
\startmode[mode1]
mode1a
\startmode[mode2]
mode2
\stopmode
mode1b % this is printed, but it should not
\stopmode
no mode
\stoptext
Cheers, Peter
--
Contact information: http://pmrb.free.fr/contact
Hi, this should be easy:
How can I access ConTeXt’s modes in Lua? Is it any different with language
modes (*en)?
e.g.
\startluacode
if context.modes['specialmode'] then
context('I’m special.')
end
\stopluacode
Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
GPG
Dear list members
I would like to disable to third column in the question when mode BL is not
enabled.
When mode BL is enabled (using the toggle), the third column should of course
appear again.
How can I achieve this?
Regards,
Jan Willem
MWE:
\starttext
%Toggles
%\enablemode[BL]
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]%
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
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, that should be documented
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: *marking
should
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, that should be documented
- something secret (maybe experimental
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 not, I'm misunderstanding its
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
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
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
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
presence of modes containing/starting with (an) alphannumeric
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) the
presence of modes containing/starting
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
(1.2) Is there a way to call the modelist and submit
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, just what the console and memory permit
(1.2) Is there a way to call the modelist and submit
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:
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
Alan Stone wrote:
On Sat, Sep 20, 2008 at 6:07 PM, Hans Hagen [EMAIL PROTECTED] 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
On Thu, Sep 11, 2008 at 12:46 PM, Hans Hagen [EMAIL PROTECTED] 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
Alan Stone wrote:
On Thu, Sep 11, 2008 at 12:46 PM, Hans Hagen [EMAIL PROTECTED] 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
Hi Hans,
can you add the systemmodes for products, components etc. in MkIV because they
are missing.
\startproduct test
\doifmodeelse{*product}{YES}{NO}
\stopproduct
Wolfgang
___
If your question is of interest to
[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) use a separate file where you
[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);
so you can map say ctrl-F10
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 file where you set the mode, and load the file
Hans
)
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 include modes with one of the various compiling commands?
no, but you can
(1) temporary put
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
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
-
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 modes -)
isn't that in mmodes.pdf ? must check
Hans
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
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
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
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
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
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
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
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,
On Mon, Sep 29, 2008 at 10:37 PM, Hans Hagen [EMAIL PROTECTED] wrote:
Alan Stone wrote:
On Thu, Sep 11, 2008 at 12:46 PM, Hans Hagen [EMAIL PROTECTED] wrote:
Alan Stone wrote:
(2.2) How does ConTeXt handle a modefile ? Are the modes parsed into a
modelist ( re: question 1.2 ) ?
best
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
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 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
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 used modes are printed on the
first page
of the document like
[screen
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
Peter Münster wrote:
Hello,
Here is a problem with nested modes:
\starttext
no mode
\startmode[mode1]
mode1a
\startmode[mode2]
mode2
\stopmode
mode1b % this is printed, but it should not
\stopmode
no mode
\stoptext
indeed, will never work, when nested use \startlocalmode
Hi,
I have the following minimal not-working example:
\starttext
\startitemize
\item One
\startmode[modeA]
\item Two
\startitemize
\startmode[modeB] % <- this
\item Two A % <- does
\stopmode % <- not work
% \doifmode{modeB}{\item Two A} % <- this
if tex.modes['specialmode'] then
context('I’m special.')
end
Best greetings,
Massi
> Hi, this should be easy:
>
> How can I access ConTeXt’s modes in Lua? Is it any different with
> language modes (*en)?
>
> e.g.
>
> \startluacode
>
> if context.modes['sp
On 05/31/2017 11:03 AM, MF wrote:
> if tex.modes['specialmode'] then
> context('I’m special.')
> end
>
> Best greetings,
> Massi
>
>> Hi, this should be easy:
>>
>> How can I access ConTeXt’s modes in Lua? Is it any different with
>> language m
On 5/31/2017 4:51 PM, Pablo Rodriguez wrote:
On 05/31/2017 11:03 AM, MF wrote:
if tex.modes['specialmode'] then
context('I’m special.')
end
Best greetings,
Massi
Hi, this should be easy:
How can I access ConTeXt’s modes in Lua? Is it any different with
language modes (*en
Thank you all!
Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
GPG Key ID 1C9B22FD
Am 2017-05-31 um 18:57 schrieb Hans Hagen <pra...@wxs.nl>:
> On 5/31/2017 4:51 PM, Pablo Rodriguez wrote:
>> This is the way to detect system modes, but I don’t
On 05/31/2017 04:51 PM, Pablo Rodriguez wrote:
> [...]
> This is the way to detect system modes, but I don’t know how to do it
> for \mainlanguage (**en).
It was simple (not even using tex.systemmodes):
\mainlanguage[es]
\starttext
\en\startlua
if tex.m
Jan Willem Flamma schrieb am 07.09.18 um 20:01:
Thank you Wolfgang.
When comparing the results between tabulate and TABLE, I noticed some different
results in formatting.
1. When using TABLE the table text is slightly shifted to the right. My initial
guess was that this is due to the frame
of the table
varies. It is larger when using tabulate.
4. The vertical space between the lines in the table text also varies. It is
larger when using TABLE.
(I left out the modes in MWE below because I don’t think it is relevant here.)
\starttext
\setupwhitespace[big]
\startsetups [tablesetups
You can’t do this with tabulate but it’s possible with natural tables.
%\enablemode [BL]
\starttext
\startsetups [tablesetups]
\setupTABLE [start] [frame=off]
\setupTABLE [column] [1] [width=6cm,align=flushleft]
\setupTABLE [column] [2] [width=2cm,align=flushleft]
\stopsetups
Thank you again Wolfgang.
Yet another question:
I like to get rid of the \par and tried integrating it into the tablesetups
somehow. I've tried adding things like before={\blank} and before\par but
couldn’t get it to work.
\starttext
\startsetups [tablesetups]
\setupTABLE [start]
Just use a empty line before the table.
Wolfgang
Jan Willem Flamma schrieb am 10.09.18 um 11:49:
Thank you again Wolfgang.
Yet another question:
I like to get rid of the \par and tried integrating it into the tablesetups
somehow. I've tried adding things like before={\blank} and before\par
Dear list members, Is it possible to combine modes and MetaFun? In the below MWE, the \doifmode construction does not work. Kind regards,Jan Willem Flamma ===\enablemode[en]%\enablemode[nl] \starttext \startbuffer[square] u := 2cm ; draw unitsquare scaled u ; drawdblarrow (0,-0.2u)..(u
On 11-11-2011 16:02, Wolfgang Schuster wrote:
Hi Hans,
can you add the systemmodes for products, components etc. in MkIV because they
are missing.
\startproduct test
\doifmodeelse{*product}{YES}{NO}
\stopproduct
I've added it but it needs checking as we need to push/pop modes (so
as we need to push/pop modes (so there is
now also \pushmode \popmode).
I have a hard time imagining a situation where push/pop modes will be
useful. It it just so that we can avoid a group?
Aditya
___
If your
}{NO}
\stopproduct
I've added it but it needs checking as we need to push/pop modes (so
there is now also \pushmode \popmode).
I have a hard time imagining a situation where push/pop modes will be
useful. It it just so that we can avoid a group?
indeed and in this case, environments and such are definitely
{*product}{YES}{NO}
\stopproduct
I've added it but it needs checking as we need to push/pop modes (so
there is now also \pushmode \popmode).
I have a hard time imagining a situation where push/pop modes will be
useful. It it just so that we can avoid a group?
indeed and in this case, environments
On 12-11-2011 13:03, Jaroslav Hajtmar wrote:
Hello, Hans.
Did not make a change now (in project structure)? I've updated an thirty
minutes ago ConTeXt and stopped me working translation of things that I
have a few days in order compiled.
fixed
It is possible to go some way older install
OK... thanx
I'm sorry to bother you., but give the corrected version to download soon?
I am not working at the moment the project.
Thanks Jaroslav.
Dne 12.11.2011 13:46, Hans Hagen napsal(a):
On 12-11-2011 13:03, Jaroslav Hajtmar wrote:
Hello, Hans.
Did not make a change now (in project
On 12-11-2011 13:55, Jaroslav Hajtmar wrote:
OK... thanx
I'm sorry to bother you., but give the corrected version to download soon?
I am not working at the moment the project.
normally the garden syncs on the (half) hour
Hans
Hello Hans.
Is it possible that I'm still not working? I just updated and always
ends the same compilation error.
My older projects do not compile. It can be a problem in anything else?
When I ignore the error message, then finally generates a PDF file, but
the first three rows in PDF file
...@gyza.cz
To: Hans Hagen pra...@wxs.nl
Cc: mailing list for ConTeXt users ntg-context@ntg.nl
Sent: Sunday, November 13, 2011 12:06 PM
Subject: Re: [NTG-context] Project structure and modes
Hello Hans.
Is it possible that I'm still not working? I just updated and always ends the
same compilation
Am 13.11.2011 um 13:36 schrieb Salil Sayed:
Hi,
I get a similar error with a beta updated today. See below.
core-env.mkiv (line 226):
-\def\resetsystemmode#1%
+\def\popsystemmode#1%
{\ifcsname\@mode@:\systemmodeprefix#1\endcsname
Thanks Wolfgang, but unfortunately for me it still does not work...
Jaroslav
Dne 13.11.2011 14:13, Wolfgang Schuster napsal(a):
-\def\resetsystemmode#1%
+\def\popsystemmode#1%
{\ifcsname\@mode@:\systemmodeprefix#1\endcsname
Am 13.11.2011 um 14:38 schrieb Jaroslav Hajtmar:
Thanks Wolfgang, but unfortunately for me it still does not work…
Minimal example:
\startcomponent test
\input knuth
\stopcomponent
With the current beta this fails but after I changed
\def\resetsystemmode#1%
Thanks many times Wolfgang.
You were right! I forgot to regenerate the format in the standalone
version, respectively I instead regenerated ConTeXt format in TeXLive
2011, which you probably assumed in your mail :-).
Everything is in order now.
Thanks again.
Jaroslav
Dne 13.11.2011
Hullo,
I'm working on my thesis (and it's pf_ul styling[1]) and I tried to include
modes.
The thing is that modes seem to be set right and work when invoked in CLI
(e.g. 'context --mode=osnutek,zaslon diplomska.tex', but ConteXt seems to
completely igonore lines in text such as:
\enablemode
Am 24.10.2010 um 21:21 schrieb Matija Šuklje:
Hullo,
I'm working on my thesis (and it's pf_ul styling[1]) and I tried to include
modes.
The thing is that modes seem to be set right and work when invoked in CLI
(e.g. 'context --mode=osnutek,zaslon diplomska.tex', but ConteXt seems
Dne nedelja 24. oktobra 2010 ob 21:27:58 je Wolfgang Schuster napisal(a):
Do you enable the mode before it is used or after it, e.g.
That did it, thanks :)
Cheers,
Matija
--
gsm:+386 41 849 552
www:http://matija.suklje.name
xmpp: matija.suk...@gabbler.org
signature.asc
Hello,
is it possible to escape from modes (fonts) defined in \starttabulate[...]? I
mean just for header - to escape the math mode and to switch to normal font
temporarily:
---
\starttext
I get:
\starttabulate[|lT|mc|p|]
\NC Code \NC Symbol\NC Description \NC\NR
\HL
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
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
Dear all,
I have two questions regarding using spacing in enumerations.
Depending on a mode being enabled, I would like to add a command at
the beginning of
an enumeration (I want to place something in the margin, but it
doesn't actually matter what I do, only when).
As shown in the
On 11/17/2016 11:21 AM, Christoph Reller wrote:
Hi,
I have the following minimal not-working example:
\starttext
\startitemize
\item One
\startmode[modeA]
\item Two
\startitemize
\startmode[modeB] % <- this
\item Two A % <- does
\stopmode % <- not work
On Thu, Nov 17, 2016 at 13:14:49 +0100 Hans Hagen wrote:
>
> On 11/17/2016 11:21 AM, Christoph Reller wrote:
> > Hi,
> >
> > I have the following minimal not-working example:
> >
> > \starttext
> > \startitemize
> > \item One
> > \startmode[modeA]
> > \item Two
> >
On Sun, Dec 18, 2016 at 9:19 PM, Mikael P. Sundqvist wrote:
> Dear list,
>
> I just realized that the very nice articles in "Nieuw archief voor
> Wiskunde" (see
> http://www.nieuwarchief.nl/serie5/index.php?deel=17=4=1
> ) are typeset with ConTeXt (at least it says so at
>
Dear list,
I just realized that the very nice articles in "Nieuw archief voor
Wiskunde" (see
http://www.nieuwarchief.nl/serie5/index.php?deel=17=4=1
) are typeset with ConTeXt (at least it says so at
http://www.nieuwarchief.nl/homeitems.php?onderwerp=2=1).
I get curious. Does anyone here know
Consider the following example:
When this is run with --mode=vim, all is well. When the mode is not set,
compilation fails. I suspect that the parser is scanning for the closing
curlie of \inlineTEX but never sees it.
\starttext
\startmode[vim]
\usemodule[t-vim]
te:
> > >
> > > Hi!
> > >
> > > I am writing notes for my teaching and would like to do the following
> with modes:
> > >
> > > * If the file is compiled with context file.tex then everything (i.e.
> the content in all modes) is typeset.
> > &
>>> Le lun. 27 août 2018 à 20:47, Henning Hraban Ramm a
>>> écrit :
>>>
>>>> Am 2018-08-27 um 16:37 schrieb Mikael P. Sundqvist :
>>>>
>>>> > > On 27 Aug 2018, at 14:14, Mikael P. Sundqvist
>>>> wrote:
>>>>
>> > >
>>> > > Hi!
>>> > >
>>> > > I am writing notes for my teaching and would like to do the
>>> following with modes:
>>> > >
>>> > > * If the file is compiled with context file.tex then everything
1 - 100 of 140 matches
Mail list logo