From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Re: Do typescripts slow down ConTeXt?
Date: Mon, 29 Sep 2003 12:58:36 +0200 [thread overview]
Message-ID: <5.2.0.9.1.20030929125728.0237ac40@server-1> (raw)
In-Reply-To: <a05210600bb9dba214556@[217.184.8.20]>
At 12:39 29/09/2003 +0200, you wrote:
>Hans Hagen <pragma@wxs.nl> wrote:
>
> > i admit that typescripts are not fast, but the advantages of the current
> > method is that i can change them easily as well as use different criteria
> > when loading them; i did some experiments with (memory hungry) preloading,
> > but on my system it made no real difference; normally the filesystem caches
> > the files quite well; file searching may take a while when the file table
> > (mktexlsr) is not up to date
>
>OK, but how can I at least switch off loading parts (typescripts, map
>files... see below) that I don't need?
>
>I didn't dare to go to the source and comment in/out lines myself.
you can of course make a minimal typescript file and then load only that
one by setting:
\def\typescriptfiles{yourfile.tex}
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2003-09-29 10:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 10:39 Steffen Wolfrum
2003-09-29 10:58 ` Hans Hagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-28 11:44 Steffen Wolfrum
2003-09-28 12:18 ` Patrick Gundlach
2003-09-29 8:52 ` 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=5.2.0.9.1.20030929125728.0237ac40@server-1 \
--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).