From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: texexec.pl and non-local .tex files
Date: Mon, 05 Oct 1998 11:39:44 +0100 [thread overview]
Message-ID: <3618A1F0.A3C71B01@wxs.nl> (raw)
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
-----------------------------------------------------------------
next reply other threads:[~1998-10-05 10:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-05 10:39 Hans Hagen [this message]
2002-10-23 16:37 Gilbert van den Dobbelsteen
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=3618A1F0.A3C71B01@wxs.nl \
--to=pragma@wxs.nl \
--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).