From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Subject: Re: new version
Date: Thu, 26 May 2005 22:57:35 +0100 [thread overview]
Message-ID: <20050526215735.21022@mail.comp.lancs.ac.uk> (raw)
In-Reply-To: <42949B00.2040305@wxs.nl>
Hans Hagen said this at Wed, 25 May 2005 17:34:24 +0200:
> the next (main) release will probably have a new texexec (ruby
>version, smoother, faster, more clever, no ini file etc)
Hmm. I hand-updated to the latest, and now texexec wants to rebuild the
format on every run.
I'm not used to seeing this, anyone have any hints on where to poke around?
(the format is in texmf.local/web2c/ and in a pdfetex subdir. I've
texhashed, too.)
adam
fixing texformat path : .:{/Users/atl/Library/texmf,!!/usr/local/teTeX/
share/texmf.local,!!/usr/local/teTeX/share/texmf.gwtex,!!/usr/local/
teTeX/share/texmf.tetex,!!/usr/local/teTeX/share/texmf}/web2c/{$ENGINE,}/{,}//
0
executable : pdfetex
format : cont-en
inputfile : llll
output : pdftex
interface : en
current mode : none
TeX run : 1
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
\write18 enabled.
(/usr/local/teTeX/share/texmf.local/web2c/natural.tcx)
kpathsea: Running mktexfmt cont-en.fmt
fmtutil: running `pdfetex -ini -jobname=cont-en -progname=context
-8bit *cont-en.ini' ...
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (INITEX)
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Adam T. Lindsay, Computing Dept. atl@comp.lancs.ac.uk
Lancaster University, InfoLab21 +44(0)1524/510.514
Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2005-05-26 21:57 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 15:34 Hans Hagen
2005-05-25 18:42 ` Taco Hoekwater
2005-05-25 19:00 ` Hans Hagen
2005-05-25 19:25 ` Taco Hoekwater
2005-05-27 15:07 ` Taco Hoekwater
2005-05-27 18:17 ` Hans Hagen
2005-05-28 18:18 ` Stuart Jansen
2005-05-25 19:24 ` feature request:-) Idris Samawi Hamid
2005-05-25 20:06 ` Hans Hagen
2005-05-25 19:26 ` new version Idris Samawi Hamid
2005-05-25 20:07 ` Hans Hagen
2005-05-26 21:57 ` Adam Lindsay [this message]
2005-05-26 23:29 ` Hans Hagen
2005-05-27 14:49 ` Adam Lindsay
2005-05-27 18:22 ` Hans Hagen
2005-05-27 19:09 ` Adam Lindsay
2005-05-26 23:34 ` Hans Hagen
2005-05-27 13:27 ` Adam Lindsay
2005-05-27 13:45 ` Hans Hagen
2005-05-27 18:20 ` Peter Münster
2005-05-27 18:41 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2020-08-25 18:14 Hans Hagen
2020-06-10 8:02 Hans Hagen
2020-06-10 15:05 ` Alan Bowen
2008-04-10 22:24 Hans Hagen
2008-04-11 4:33 ` Aditya Mahajan
2008-04-11 7:39 ` Hans Hagen
2008-04-11 7:50 ` Wolfgang Schuster
2008-04-11 9:48 ` Hans Hagen
2004-01-13 16:41 Hans Hagen
2003-09-17 17:47 Steffen Wolfrum
2003-09-17 12:25 Steffen Wolfrum
2003-09-17 16:00 ` Hans Hagen
2003-09-17 10:50 Hans Hagen
2003-08-07 16:02 Hans Hagen
2002-07-26 22:53 Hans Hagen
2002-07-27 19:34 ` Jens-Uwe Morawski
2002-07-29 7:15 ` Hans Hagen
2002-07-29 9:09 ` Jens-Uwe Morawski
2002-07-29 9:33 ` Hans Hagen
2002-07-30 9:56 ` Jens-Uwe Morawski
2002-07-30 21:06 ` Hans Hagen
2002-07-31 8:29 ` Jens-Uwe Morawski
2000-09-21 16:33 Hans Hagen
2000-01-24 11:13 Hans Hagen
2000-01-24 11:42 ` Mr. Wang Lei
2000-01-24 12:24 ` Tobias Burnus
2000-01-24 15:45 ` Hans Hagen
2000-01-24 15:32 ` Hans Hagen
2000-01-24 11:44 ` Tobias Burnus
2000-01-24 15:47 ` 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=20050526215735.21022@mail.comp.lancs.ac.uk \
--to=atl@comp.lancs.ac.uk \
--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).