From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Subject: Re: Re: textext() doesn't work on my MikTeX distr.
Date: Fri, 15 Oct 2004 16:27:42 +0100 [thread overview]
Message-ID: <20041015162742.11476@news.comp.lancs.ac.uk> (raw)
In-Reply-To: <416FB036.7080003@email.si>
Mojca Miklavec said this at Fri, 15 Oct 2004 13:10:46 +0200:
>Thanks a lot to both of you. It finally works. The line I had to change
>was in miktex.ini. (I never had to bother about MikTeX specific issues
>till now and I didn't expect the problem to lie so deep in the system.)
I found it bad to do this so deep in the system as well. I found a way
that enables \write18 only for ConTeXt, using the texexec configuration
file. I documented it at:
<http://contextgarden.net/Texexec.ini>
Basically, you would change texexec.ini so that it had the line:
for miktex set TeXPassString to --alias=context -shell-escape
...is there any reason why this wouldn't work for MikTeX?
or, for that matter, for general ConTeXt use?
>Would it make sense to add just a short hint for newbies
>somewhere at the beginning of the manual, warning that write18 has to be
>enabled in order to process some graphics properly?
:) I suppose Hans could, but it would mean fewer people come join the
ConTeXt community...
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Adam T. Lindsay, Computing Dept. atl@comp.lancs.ac.uk
Lancaster University, InfoLab21 +44(0)1524/510.514
Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2004-10-15 15:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <416D1849.9080106@guest.arnes.si>
2004-10-13 14:38 ` Patrick Gundlach
2004-10-15 3:36 ` Mojca Miklavec
2004-10-15 7:37 ` Patrick Gundlach
2004-10-15 7:38 ` Hans Hagen
2004-10-15 11:10 ` Mojca Miklavec
2004-10-15 15:27 ` Adam Lindsay [this message]
2004-10-15 16:21 ` 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=20041015162742.11476@news.comp.lancs.ac.uk \
--to=atl@comp.lancs.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).