Hans Hagen wrote:
> well, opening files and overwriting them can be done anyway
That's true. Though the default teTeX setup seems to be (from
texmf.cnf):
% Allow TeX \openin, \openout, or \input on filenames starting with `.'
% (e.g., .rhosts) or outside the current tree (e.g., /etc/passwd)?
Hans Hagen wrote:
> Sanjoy Mahajan wrote:
> > Actually, on my system (Ubuntu, a Debian derivative), changing the
> > texmf.cnf file directly is not a good idea. Instead one should change
> > the same line in /etc/texmf/texmf.d/95NonPath.cnf and then run
> > 'update-texmf' as root to generate the t
Sanjoy Mahajan wrote:
> Actually, on my system (Ubuntu, a Debian derivative), changing the
> texmf.cnf file directly is not a good idea. Instead one should change
> the same line in /etc/texmf/texmf.d/95NonPath.cnf and then run
> 'update-texmf' as root to generate the texmf.cnf file.
>
incredib
> Check your log file for
>
> systems : system commands are enabled
Thanks, that was the problem. It was saying 'disabled' instead. The
fix was to change /etc/texmf/texmf.cnf to enable write18. The
shell_escape line has to be set to 't' rather than 'f', i.e.:
shell_escape = t
Actuall
On Tue, 12 Sep 2006, Sanjoy Mahajan wrote:
> I'm playing with simple files in order to learn metafun. The following
> small example produces an undefined figure. It illustrates either a
> context problem or, more likely, a confusion on my part.
>
> = cut here
I'm playing with simple files in order to learn metafun. The following
small example produces an undefined figure. It illustrates either a
context problem or, more likely, a confusion on my part.
= cut here ===
\runMPgraphicstrue
\starttext
