Re: texexec.pl and non-local .tex files

Re: texexec.pl and non-local .tex files

[Hans Hagen]

Gilbert van den Dobbelsteen wrote:
> 
> 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.

I can add a switch --global that does not do the test. Can you test if
things work ok when you comment the if (-e "$JobName.tex") line(s)? 

Hans

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
    tel: 038 477 53 69 | fax: 038 477 53 74 | mail: pragma@wxs.nl
-----------------------------------------------------------------

texexec.pl and non-local .tex files

[Gilbert van den Dobbelsteen]

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.