ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
Subject: Re: runMPgraphicstrue produces undefined figure
Date: Wed, 13 Sep 2006 05:12:02 +0100	[thread overview]
Message-ID: <E1GNM6U-0002QB-00@skye.ra.phy.cam.ac.uk> (raw)
In-Reply-To: Your message of "Tue, 12 Sep 2006 18:07:24 EDT." <Pine.WNT.4.63.0609121802570.712@nqvgln>

> 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

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.

Warning: If you've enabled 'shell_escape', then don't run *TeX on
untrusted files, in case they do anything malicious like 'rm -fr /'.

Also now I see how I got fooled into thinking that write18 was already
enabled.  The one-line tex file from metafun-s.pdf contains
\immediate\write18{echo It works}.  When run it produces an "It works"
whether or not write18 is enabled.  If disabled:

(./3.tex
echo It works
 )

which made me think that all was okay.  If enabled you get this:

 \write18 enabled.
(./3.texIt works
 )

-Sanjoy

`Never underestimate the evil of which men of power are capable.'
         --Bertrand Russell, _War Crimes in Vietnam_, chapter 1.

  reply	other threads:[~2006-09-13  4:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-12 21:39 Sanjoy Mahajan
2006-09-12 22:07 ` Aditya Mahajan
2006-09-13  4:12   ` Sanjoy Mahajan [this message]
2006-09-13  7:34     ` Hans Hagen
2006-09-13 13:32       ` Sanjoy Mahajan
2006-09-13 13:38       ` Sanjoy Mahajan

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=E1GNM6U-0002QB-00@skye.ra.phy.cam.ac.uk \
    --to=sanjoy@mrao.cam.ac.uk \
    --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).