From: Ed L Cashin <ecashin@terry.uga.edu>
Cc: ntg-context@ntg.nl
Subject: Re: fast texshow!
Date: 30 Oct 2001 11:09:32 -0500 [thread overview]
Message-ID: <m3y9ltyurn.fsf@terry.uga.edu> (raw)
In-Reply-To: <20011030092557.154f4742.taco@elvenkind.com>
Taco Hoekwater <taco@elvenkind.com> writes:
> The only reason I can think of: You accidentally installed a new CPU
> as well? :)
Hmm. The change was so dramatic that I thought it had to be texshow
itself. The difference in the system is that I've switched to
FreeBSD-4.4-STABLE from RedHat.
> Seriously, which context? My texshow still is version 0.1 (1999) and
> just as slow as before. And I thought I *had* the latest context...
I'm not at home, so I can't check right now, but it was the beta from
the ntg mirror, downloaded a couple of days ago.
--
--Ed Cashin PGP public key:
ecashin@terry.uga.edu http://www.terry.uga.edu/~ecashin/pgp/
next prev parent reply other threads:[~2001-10-30 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-30 5:10 Ed L Cashin
2001-10-30 8:25 ` Taco Hoekwater
2001-10-30 12:25 ` Hans Hagen
2001-10-30 16:09 ` Ed L Cashin [this message]
2001-10-31 8:58 ` Taco Hoekwater
2001-10-31 16:17 ` Ed L Cashin
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=m3y9ltyurn.fsf@terry.uga.edu \
--to=ecashin@terry.uga.edu \
--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).