From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Why are all the typescripts accessed?
Date: Tue, 24 May 2005 23:54:45 +0200 [thread overview]
Message-ID: <4293A2A5.1070801@wxs.nl> (raw)
In-Reply-To: <200505241345.52748.john@wexfordpress.com>
John R. Culleton wrote:
> When I texexec a file the names of all the typescripts
> on the system scroll by. Is something set up wrong? This slows
> down each run significantly.
>
> I run Slackware Linux and the TeX package from Slack-Current.
> Texexec alleges that it is version 5.2.4.
typescripts can be large and would take much memory if loaded by default
i recently added
\preloadtypescripts
you can add that to your cont-sys.tex (or style) file if you like; it indeed
speeds up tings noticably
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
prev parent reply other threads:[~2005-05-24 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 13:45 John R. Culleton
2005-05-24 21:54 ` Hans Hagen [this message]
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=4293A2A5.1070801@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).