From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/152
Path: main.gmane.org!not-for-mail
From: Gilbert van den Dobbelsteen <GILBERT@login.iaf.nl>
Newsgroups: gmane.comp.tex.context
Subject: texexec.pl and non-local .tex files
Date: Wed, 23 Oct 2002 16:37:04 +0000 (UTC)
Sender: owner-ntg-context@let.uu.nl
Message-ID: <3614d0aa.login@login.iaf.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 1035391024 21664 80.91.224.250 (23 Oct 2002 16:37:04 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Wed, 23 Oct 2002 16:37:04 +0000 (UTC)
Original-To: ntg-context@ntg.nl
Xref: main.gmane.org gmane.comp.tex.context:152
X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:152

Hi there,

I am encountering a problem using texexec. I have a file mod.tex, 
located somewhere on my system. This file basically is a convertor. 
It's (conceptual) input:

\starttext
\typefile[history.txt]
\stoptext

I need this to quickly generate a .pdf file from an history.txt file, 
which are located throughout all our projects.

When running this manually, e.g.:

pdftex &cont-nl mod

it works, because mod.tex is found where I placed in (in 
c:/tex/pragma/sources/local/mod.tex). But when running it through 
texexec.pl it doesn't. 

texexec --pdf mod

Looking inside the texexec.pl script, I see that the .tex file *must*
exist in the current directory, because it is scanned by texexec for
options (which I think is a very nice idea).

Isn't it possible to run the thing through context even though the 
file doesn't exist? Or is this a bad idea? I know for sure I can change 
the perl script to do so, but perhaps am I missing a conceptual idea 
here.

Gilbert.