From: Sebastian Rooks <sebastian.rooks@free.fr>
Subject: Re: The smallest instalation for work with ConTeXt and MetaFun (TeXLive8) ?
Date: Mon, 06 Oct 2003 09:07:10 +0200 [thread overview]
Message-ID: <3F81149E.9060509@free.fr> (raw)
In-Reply-To: <12145447640.20031006043522@emil.teleton.pl>
^Nitram^ wrote:
>Hi,
>
>Anybody has an experience with TeXLive (8 or 7) - what is the smallest
>installation type for working with ConTeXt and (absolutely necessary)
>MetaFun - I tried 'generic basic' and 'generic recommended' but I
>can't make MP graphics - I have a problem with it again ;(
>
>Of course 'full' installation works fine, but I have no idea what I
>need in smaller installation to working fine...
>
>Probably I forgot change something (again) in config files - in log I
>have:
>This is pdfeTeXk, Version 3.141592-1.11a-2.1 (Web2c 7.5.2) (format=cont-en 2003.10.6) 6 OCT 2003 04:15
>entering extended mode
> %&-line parsing enabled.
>...
>\openout0 = `_back-mpgraph.mp'.
>\openout0 = `_back-mprun.mp'.
>\openout0 = `mpgraph.mp'.
>\openout0 = `mprun.mp'.
>...
>[MP to PDF] (./_back-mpgraph.1) [2.2]
>\openout5 = `_back-mpgraph.mp'.
>mpost -progname=mpost -mem=metafun _back-mpgraph
>system()...disabled.
>
>...
>
>and no graphic in pdf. But when I run mpost _back-mpgrapg.mp I have
>_back-mpgraph.1 file and another run of context includes graphic (this
>one) to pdf. What may be wrong ?
>
>
>
It seems you didn't enable system commands via \write18{...}.
In your texmf-local\web2c\texmf.cnf do you have (as stated page 9 of
minstall.pdf):
* The WEB2C configuration *
Although not stricktly needed, ConTEXt will operate more smoothly when
these features are set in the file texmf.cnf.
openout_any = a
shell_escape = t
allow_multiple_suffixes = f
The first line permits ConTEXt to open parent paths that can hold common
styles.
The second line enables enables users to embed METAPOST code in their
document.
As a result, METAPOST is called automatically. The last line makes sure
that when
opening files like somefile.tuo, TEX will not try to open
somefile.tuo.tex first.
When you embed TEX code in a METAPOST definition, using btex ... etex,
the next
line will use TEXexec to process that fragment in the case of using
METAPOST directly.
MPXCOMMAND=texexec mptex
Does it help you ?
Seb.
next prev parent reply other threads:[~2003-10-06 7:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 2:35 ^Nitram^
2003-10-06 7:07 ` Sebastian Rooks [this message]
2003-10-06 8:20 ` Hans Hagen
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=3F81149E.9060509@free.fr \
--to=sebastian.rooks@free.fr \
--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).