From: Erik Frambach <E.H.M.Frambach@eco.rug.nl>
Subject: texexec
Date: Thu, 22 Apr 1999 11:05:22 +0200 [thread overview]
Message-ID: <199904220905.LAA01171@dep.eco.rug.nl> (raw)
Under Windows texexec.pl does not function very well because of:
my $IniPath = `kpsewhich --format='other text files' -progname=context
texexec.ini` ;
Thee '-quotes around 'other text files' should be "-quotes, or you will
get the wrong answer from kpsewhich! I don't know if using " will break
the script on Unix?
Another problem: this one works just fine:
pdftex.exe -progname=context "&cont-nl" file.tex
but this one does not:
perl.exe texexec.pl --interface=nl file.tex
"tex capacity exceeded" (strings and pool size): that's because
"-progname=context" is not there. In texmf.cnf there are many
".context" specifications, a few ".cont-nl", but not when it comes
to memory settings. I think it would be wise (or at least more safe)
to add "-progname=context" to texexec.pl when running a tex job!
I know, there is no good reason not to use hugetex, but the current
(tex live 4) texmf.cnf still assumes low memory settings.
Greetings,
Erik Frambach
next reply other threads:[~1999-04-22 9:05 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-22 9:05 Erik Frambach [this message]
1999-04-22 11:31 ` texexec Erik Frambach
1999-04-22 12:12 ` texexec Taco Hoekwater
1999-04-22 12:13 texexec Thomas Esser
1999-04-22 14:28 ` texexec Taco Hoekwater
1999-04-22 12:31 texexec Thomas Esser
1999-04-23 7:09 ` texexec Hans Hagen
[not found] <375383E9.3A6BF93E@wxs.nl>
1999-06-01 19:34 ` texexec David Arnold
1999-06-02 7:26 ` texexec Hans Hagen
2000-02-08 6:16 TeXexec Dan Seracu
2000-02-08 8:33 ` TeXexec Gilbert van den Dobbelsteen
2000-02-08 9:33 ` TeXexec Dan Seracu
2001-02-10 19:02 texexec Giuseppe Bilotta
2001-02-11 8:23 ` texexec Marc van Dongen
2001-02-11 21:14 ` texexec Hans Hagen
2001-02-12 16:35 ` texexec Ed L Cashin
2001-02-12 18:48 ` texexec Taco Hoekwater
2002-12-09 14:56 texexec Matthew Huggett
2002-12-09 19:25 ` texexec Henning Hraban Ramm
2003-06-12 13:04 texexec Raimund Kohl-Fuechsle
[not found] <"from Raimund.Kohl"@freenet.de>
2003-06-12 13:18 ` texexec Raimund Kohl
2003-06-12 15:01 ` texexec Ed L Cashin
2003-06-14 9:30 ` texexec Hans Hagen
2003-06-14 11:27 ` texexec Siep Kroonenberg
2003-06-13 15:57 ` texexec Raimund Kohl-Fuechsle
2003-06-13 16:00 ` texexec Raimund Kohl
[not found] <Pine.LNX.4.44.0307012300450.9436-100000@twain.marshallward .net>
2003-07-02 18:08 ` Texexec Hans Hagen
2003-07-04 23:39 ` Texexec Marshall Ward
2006-05-04 22:03 texexec Hans Hagen
2006-05-04 23:59 ` texexec Jilani Khaldi
2006-05-05 6:10 ` texexec luigi scarso
2006-05-05 13:26 ` texexec Steve Grathwohl
2006-05-05 13:36 ` texexec Renaud AUBIN
2006-05-05 15:16 ` texexec Hans Hagen
2006-05-05 14:09 ` texexec Steve Peter
2006-05-06 23:01 ` texexec Aditya Mahajan
2006-05-07 18:14 ` texexec Hans Hagen
2006-05-07 18:34 ` texexec Aditya Mahajan
2006-05-07 21:15 ` texexec Hans Hagen
2006-05-08 0:37 ` texexec Aditya Mahajan
2006-05-07 19:10 ` texexec Hans Hagen
2006-05-07 19:29 ` texexec Aditya Mahajan
2006-05-07 19:13 ` texexec Hans Hagen
2006-05-07 19:30 ` texexec Aditya Mahajan
2006-05-07 21:53 ` texexec Mojca Miklavec
2006-05-15 22:55 ` texexec frantisek holop
2006-05-15 23:06 ` texexec Hans Hagen
2006-06-19 21:46 ` texexec John R. Culleton
2006-06-19 21:13 ` texexec Hans Hagen
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=199904220905.LAA01171@dep.eco.rug.nl \
--to=e.h.m.frambach@eco.rug.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).