From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Modes in MkIV minimals (bug?)
Date: Sun, 24 Oct 2010 21:27:58 +0200 [thread overview]
Message-ID: <03C7108D-AD8E-476A-991F-F4D874A3BC98@gmail.com> (raw)
In-Reply-To: <201010242121.46604.matija@suklje.name>
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 to
> completely igonore lines in text such as:
>
> \enablemode[osnutek]
>
> Is this a bug or am I doing something wrong?
Do you enable the mode before it is used or after it, e.g.
\enablemode[foo]
\startmode[foo]
...
\stopmode
use the content of the mode „foo“ while
\startmode[foo]
...
\stopmode
\enablemode[foo]
doesn’t use it because at the time the mode was called it was disabled and the \enablemode has therefore no effect because it’s calles to late.
If this doesn’t apply to you make a minimals example.
Wolfgang
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-10-24 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-24 19:21 Matija Šuklje
2010-10-24 19:27 ` Wolfgang Schuster [this message]
2010-10-24 19:48 ` Matija Šuklje
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=03C7108D-AD8E-476A-991F-F4D874A3BC98@gmail.com \
--to=schuster.wolfgang@googlemail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).