From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/1621 Path: main.gmane.org!not-for-mail From: "Erik Frambach" Newsgroups: gmane.comp.tex.context Subject: Re: installing Context Date: Thu, 3 Feb 2000 09:12:53 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <200002030813.JAA18553@dep.eco.rug.nl> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Trace: main.gmane.org 1035392443 1872 80.91.224.250 (23 Oct 2002 17:00:43 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 17:00:43 +0000 (UTC) Original-To: ntg-context@ntg.nl Xref: main.gmane.org gmane.comp.tex.context:1621 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:1621 > Further investigation suggests that the version of ActiveState Perl that I > am using (dating back to August 1999) does not seem to read the PATH > environment. The following in autoexec.bat should work, but doesn't on my > PC: > > SET PATH=%PATH%;C:\TEXMF\CONTEXT\CONFIG;C:\TEXMF\CONTEXT\PERLTK > SET PATH=%PATH%;C:\TEXMF\MIKTEX\BIN;C:\PERL\BIN > > ie perl texexec.pl --make en de produces the message > > Can't open perl script "texexec.pl": No such file or directory Perl *is* found using the PATH here. It's Perl itself that complains that it can't find the file texexec.pl. If you store texexec.pl somewhere on the PATH, you can run it like this: perl -S texexec.pl -S means that Perl will look for the script along the PATH. Greetings, Erik