From: Taco Hoekwater <taco@elvenkind.com>
Cc: ntg-context@ntg.nl
Subject: Re: long texexec run
Date: Fri, 12 Oct 2001 11:50:03 +0200 [thread overview]
Message-ID: <20011012115003.0ff57f40.taco@elvenkind.com> (raw)
In-Reply-To: <5.1.0.14.0.20011012111100.00a9a168@pop.t-online.de>
IIRC, miktex uses the registry for all sorts of things. So perhaps cleaning
the registry might help (well, that would mean re-installing windows I guess)?
> I started using context with miktex 2.1, then switched to fptex. I remember
> that I was surprised about the fact that my documents compile significantly
> faster with fptex. I can't tell the exact difference (perhaps 1,5--2 times
> faster), nor the reason, but maybe you want to try it.
>
> Eckhart
--
groeten,
Taco
next prev parent reply other threads:[~2001-10-12 9:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 11:00 Karsten Hachmeister
2001-10-10 13:53 ` Hans Hagen
[not found] ` <006501c151bf$2bb37870$695f298d@fhwolfenbuettel.de>
2001-10-11 7:06 ` Hans Hagen
2001-10-11 10:41 ` Karsten Hachmeister
2001-10-11 11:37 ` Taco Hoekwater
2001-10-11 12:29 ` Karsten Hachmeister
2001-10-11 14:49 ` Hans Hagen
2001-10-11 20:02 ` Karsten Hachmeister
2001-10-12 6:59 ` Hans Hagen
2001-10-12 9:16 ` Eckhart Guthöhrlein
2001-10-12 9:50 ` Taco Hoekwater [this message]
2001-10-12 14:07 ` Karsten Hachmeister
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=20011012115003.0ff57f40.taco@elvenkind.com \
--to=taco@elvenkind.com \
--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).