* texexec.pl and non-local .tex files
@ 2002-10-23 16:37 Gilbert van den Dobbelsteen
0 siblings, 0 replies; 2+ messages in thread
From: Gilbert van den Dobbelsteen @ 2002-10-23 16:37 UTC (permalink / raw)
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: texexec.pl and non-local .tex files
@ 1998-10-05 10:39 Hans Hagen
0 siblings, 0 replies; 2+ messages in thread
From: Hans Hagen @ 1998-10-05 10:39 UTC (permalink / raw)
Cc: ntg-context
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
-----------------------------------------------------------------
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-10-23 16:37 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-10-23 16:37 texexec.pl and non-local .tex files Gilbert van den Dobbelsteen
-- strict thread matches above, loose matches on Subject: below --
1998-10-05 10:39 Hans Hagen
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).