From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/386 Path: main.gmane.org!not-for-mail From: Erik Frambach Newsgroups: gmane.comp.tex.context Subject: texexec Date: Thu, 22 Apr 1999 11:05:22 +0200 Sender: owner-ntg-context@let.uu.nl Message-ID: <199904220905.LAA01171@dep.eco.rug.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 1035391249 23655 80.91.224.250 (23 Oct 2002 16:40:49 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 16:40:49 +0000 (UTC) Original-To: context list Xref: main.gmane.org gmane.comp.tex.context:386 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:386 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